Skip to main content
In this guide, you’ll learn how to serve a fully static website—HTML, CSS, JavaScript, and media—directly from an Amazon S3 bucket. We’ll cover how static hosting works, pricing considerations, and steps to configure a custom domain.
Static website hosting on Amazon S3 supports only static files. If your site requires server-side processing, consider integrating Amazon EC2, Amazon ECS, or AWS Lambda.

​
Understanding Static Websites

When a user enters a URL, their browser sends an HTTP GET request to a web server, which responds with files that the browser renders. Common file types include: By uploading these files as objects in an S3 bucket and enabling static website hosting, you can serve them directly over HTTP.
The image is an infographic about static hosting, explaining that it allows access to website files through HTTP and provides a URL via S3. It notes that it's used only for static websites and requires a specific format for domain customization.

​
How Static Hosting Works

  1. Upload your site assets (HTML, CSS, JS, images) to an S3 bucket.
  2. In the bucket Properties, enable Static website hosting.
  3. Specify your index.html (and optional error.html) documents.
  4. Use the assigned S3 website endpoint to deliver your content.

​
Pricing Overview

Static hosting on S3 involves standard storage and data transfer fees, plus a small request charge. For example, on S3 Standard, GET requests cost $0.0004 per 1,000 requests.
The image shows a pricing table for different types of data requests and retrievals, including S3 Standard and S3 Intelligent-Tiering, with associated costs per 1,000 requests and per GB.
Factor in both storage and request fees when estimating your total hosting cost.

​
Accessing Your Static Site

After enabling static website hosting, S3 assigns an endpoint in this format:
Point your users to this URL to serve your static site directly from S3.

​
Using a Custom Domain

To replace the default S3 URL with your own domain, configure DNS using Amazon Route 53 or another provider. Your bucket name must exactly match the domain you wish to use. For example:
  • Bucket name: bestcars.com
  • Custom domain: http://bestcars.com
In Route 53, create an Alias record (or CNAME) that maps bestcars.com to your S3 website endpoint.
Your S3 bucket name must match your custom domain (example.com). If they differ, DNS routing will fail and your site will be inaccessible.
The image illustrates a process involving a custom domain name, showing a user, a Route 53 icon, a URL (http://bestcars.com), and a server.

​
Further Reading

Watch Video