DEV Community: DHANYA RAVI

Create a static website using Amazon S3

DHANYA RAVI — Fri, 18 Apr 2025 14:21:41 +0000

✅ Step 1: Prepare Your Website Files

First, I created a simple HTML file called myself.html containing my resume and personal information.
It can include HTML, CSS, and JavaScript — no backend code is needed since it’s a static website.

✅ Step 2: Create an S3 Bucket

Log in to the AWS Console.
Go to S3 under Services.
Click Create bucket.
Choose a globally unique name.
Uncheck “Block all public access”.
Enable ACLs and acknowledge the warning.
Click Create bucket.

✅ Step 3: Upload Your HTML File

Open your bucket.
Click Upload → Add your index.html.
Click Upload.

✅ Step 4: Set File Permissions

Select the uploaded file.
Click Actions > Make public.
This step is important so your file is visible to the public through the website URL.

✅ Step 5: Enable Static Website Hosting

Go to the Properties tab of your bucket.
Scroll to Static website hosting and click Edit.
Choose Enable.
Set the Index document:
If your file is named index.html, enter: index.html
Save changes.

✅ Step 6: Add a Bucket Policy (If Access Denied)

If you're getting an "Access Denied" error:
Go to the Permissions tab.
Scroll to Bucket Policy, click Edit.
Paste this policy (replace YOUR-BUCKET-NAME):
json
Copy
Edit

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "PublicReadGetObject",
"Effect": "Allow",
"Principal": "",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::YOUR-BUCKET-NAME/"
}
]
}

Click Save changes.

✅ Step 7: View Your Website! 🎉

Go back to the Static Website Hosting section.
You’ll see a bucket website endpoint and that is your Website endpoint URL.
Copy and then paste it in a new tab to see your static website.

RUNNING LINUX COMMANDS AND UPLOADING THE OUTPUT TO S3 DIRECTLY THROUGH EC2 INSTANCE

DHANYA RAVI — Fri, 24 Jan 2025 13:43:02 +0000

Step 1: Create an ec2 instance

Give a name for the ec2 instance and select amazon machine image

Create a key value pair and the instance type should be t2.micro

Once the instance is created wait until the status turns into running state

Download putty and configure it

White listing my ip address so that only I can acccess it by editing the inbound rules

Step 2: Connecting puTTy with the ec2 instance.

Go to the puTTy gen and select the pem key that was downloaded while creating the key value pair and generate it to get the private key.

In the puTTy configuration go to the SSH category and in that select admin and in that select config and then enter the public IP address and load the private key that was saved and connect.

Run the linux commands and get the output and save it in a file .

Step 3: Create roles.

Go to the create role and in the entity type select AWS service.

In the use case select ec2 and give the role name and create the role.

The role is created.

Step 4: Now go to the ec2 instance type and select the instance and in the actions go to the security option.

In the security go to the modify iam role option.

Select the role that we created and then hit update.

Now the ec2 instance will be connected to the iam role.

Step 5: Once we enter the command [aws s3 cp filename.txt s3://bucket name/] then the file will be uploaded to the bucket.

AMAZON NEPTUNE🪐

DHANYA RAVI — Thu, 23 Jan 2025 02:43:42 +0000

Amazon Neptune is a managed graph database for connected data, ideal for recommendations, social networks, and fraud detection.

KEY FEATURES✨:

Works with both Gremlin(property graphs) and SPARQL(RDF graphs).
Delivers millisecond query response times for real-time applications.
Provides multi-AZ replication with automatic failover for reliability.
Designed for 99.99% availability with built-in replication and failover.
Available in multiple AWS regions worldwide.
Offers R6g, R5, and T3 instance types for various workloads.

USE CASES🚀:

Building recommendation engines, detecting fraud patterns, analyzing social networks.
Managing knowledge graphs, optimizing IoT networks, and powering real-time personalized search results.

PRICING MODEL💰:

Amazon Neptune follows a pay-as-you-go pricing model, where you are billed based on the resources you use. Pricing is primarily based on the following:

Instance Hours: Charges depend on the type and number of instances you use and how long they are running.
Storage: You pay for the database storage used, including backup storage.
I/O Requests: You are charged for the number of read and write operations made to the database.
Data Transfer: Outbound data transfer (moving data outside of AWS) is also billed.

COMPARISON WITH SIMILAR SERVICES⚖️:

Amazon Neptune🪐 vs. Google Cloud Datastore☁️:
Neptune is a managed graph database for connected data, while Cloud Datastore is a NoSQL document database without native graph support.
Amazon Neptune🪐 vs. Azure Cosmos DB🌐:
Neptune is optimized for graph queries, whereas Cosmos DB is a multi-model database with broader use cases.
Amazon Neptune🪐 vs. Neo4j:
Neo4j is an open-source graph database that requires manual setup, while Neptune offers a fully managed, scalable, and secure service.

ADVANTAGES🌟:

High performance with millisecond query response times.
Fully managed with automated backups and scaling.
Supports both Gremlin and SPARQL for flexible graph models.
Seamless integration with AWS services.
Scalable and highly available with multi-AZ replication.

LIMITATIONS🚧:

Requires learning Gremlin or SPARQL, which can be complex.
Higher costs for small-scale use cases.
Limited third-party tool support compared to Neo4j.
Not available in all AWS regions.

CASE STUDY: THOMSON REUTERS📚💼:

Thomson Reuters, a global leader in information services, uses Amazon Neptune to power its knowledge graph, which links legal, regulatory, and tax information for professionals. Neptune enables them to handle complex relationships across vast datasets with high performance and low latency, helping users find accurate, context-rich answers efficiently. This transformation improved their data management and customer experience significantly.