How to Host Your First Static Website on AWS S3 in Under 10 Minutes

A step-by-step, zero-fluff guide for complete beginners and aspiring web developers.

Setting up your first website on Amazon Web Services (AWS) can feel intimidating with all the cloud jargon and complex dashboard options. But if you have a simple static website (built with HTML, CSS, and JavaScript), you don’t need a full virtual server. Instead, you can use Amazon S3 to host your site globally in just a few clicks.

In this practical guide, we will break down exactly how to upload your files, set permissions, and launch your site live onto the web in under 10 minutes.

1. Introduction: What is Amazon S3?

Amazon S3 (Simple Storage Service) is an object storage service designed to store files in the cloud. Think of an S3 bucket as a giant, highly secure digital storage container.

Why host a static website on S3 instead of a traditional server?

Ultra Low Cost: You only pay for the tiny fraction of storage and bandwidth you actually use. For personal sites or low-traffic portfolios, it often costs pennies per month (or is completely free under AWS Free Tier).
No Server Maintenance: You don’t need to patch operating systems, configure web servers like Nginx or Apache, or manage security updates.
High Availability & Scale: AWS automatically manages scale and reliability so your site stays up even if traffic spikes.

2. Prerequisites

Before we start, make sure you have the following ready:

An AWS Account: Sign up at aws.amazon.com if you haven’t already.
A Static Website File: At minimum, an index.html file on your computer.

Quick HTML Setup: If you don’t have a site ready, open a text editor, paste the code below, and save it as index.html:<!DOCTYPE html>

<html>

<head>

<title>My First S3 Website</title>

</head>

<h1>Hello World!</h1>

<p>My static website is officially live on AWS S3!</p>

</body>

</html>

3. Step 1: Creating an S3 Bucket

Log into your AWS Management Console and search for S3 in the top search bar.
Click the Create bucket button.
Under General configuration, enter a Bucket name.
- Note: S3 bucket names must be globally unique across all AWS users worldwide. Use lowercase letters, numbers, and hyphens (e.g., my-first-dev-website-2026).
Scroll down to Block Public Access settings for this bucket.
Uncheck the box next to Block all public access.
Check the acknowledgment box that appears below it, warning that objects in the bucket can be made public.
Leave all other default settings and click Create bucket at the bottom of the page.

Pro-Tip: S3 blocks public access by default to prevent accidental data leaks. Because we explicitly want the web to view our site files, turning off this block is required.

4. Step 2: Uploading Your Content

Now that your bucket exists, let me add the site files.

On the S3 main dashboard, click on your newly created bucket name to open it.
Click the Upload button.
Click Add files (or Add folder if you have CSS/JS asset folders). Select your index.html file.
Scroll to the bottom and click Upload.
Once the progress bar finishes, click Close to return to your bucket contents.

5. Step 3: Enabling Static Website Hosting

Uploading files isn’t enough; we need to tell AWS to serve these files as a website.

Click on the Properties tab near the top of your bucket page.
Scroll all the way down to the Static website hosting section.
Click Edit.
Choose Enable.
Under Hosting type, select Host a static website.
In the Index document field, type index.html.
(Optional) If you have an error page, you can enter error.html under Error document.
Click Save changes.

6. Step 4: Writing the Bucket Policy (Permissions)

Even though we unblocked public access in Step 1, AWS still requires a specific Bucket Policy to allow visitors to download/view the HTML files.

Click on the Permissions tab.
Scroll down to the Bucket policy section and click Edit.
Copy the following JSON block and paste it into the policy editor:

{

“Version”: “2012-10-17”,

“Statement”: [

{

“Sid”: “PublicReadGetObject”,

“Effect”: “Allow”,

“Principal”: ”*”,

“Action”: “s3:GetObject”,

“Resource”: “arn:aws:s3:::YOUR-BUCKET-NAME/*”

}

]

}

Crucial Step: Replace YOUR-BUCKET-NAME inside the code block with your actual S3 bucket name. Make sure to keep the /* at the end.
Click Save changes.

Pro-Tip: The s3:GetObject permission explicitly grants permission for anyone (*) on the internet to read and view your website files.

7. Testing Your Website

You are ready to test!

Go back to the Properties tab.
Scroll down to the Static website hosting section again.
Locate the Bucket website endpoint URL at the bottom. It will look something like this:
http://my-first-dev-website-2026.s3-website-us-east-1.amazonaws.com
Click or copy-paste that link into your web browser.

You should see your index.html page running live on the internet!

8. Troubleshooting & Common Pitfalls

Issue	Solution
403 Forbidden Error	This almost always means public access is still blocked or your Bucket Policy is incorrect. Double check that Block all public access is OFF and check for typos in your JSON policy (especially the bucket name).
404 Not Found Error	Verify that your main HTML file is named exactly index.html and is uploaded in the root of the bucket (not inside a subfolder).
Not Secure Warning (HTTP vs HTTPS)	S3 static website endpoints only support HTTP out-of-the-box. If you type https:// manually, the connection will fail.

9. Next Steps for Production

Congratulations on launching your first S3 site! If you are preparing to launch a professional portfolio or client site, consider these next steps:

Add a Custom Domain: Use AWS Route 53 or Namecheap/GoDaddy to point your own domain name (e.g., myname.com) to your bucket.
Enable HTTPS Security: Use Amazon CloudFront (AWS’s Content Delivery Network) to add free SSL certificates, serve your site via secure HTTPS, and speed up global loading times.