Amazon Simple Storage Service
Developer Guide (API Version 2006-03-01)

Example: Setting Up a Static Website Using a Custom Domain

Suppose you want to host your static website on Amazon S3. You have registered a domain, for example,, and you want requests for and to be served from your Amazon S3 content.

Whether you have an existing static website that you now want to host on Amazon S3 or you are starting from scratch, this example will help you host websites on Amazon S3.

Before You Begin

As you walk through the steps in this example, note that you will work with the following services:

Domain registrar of your choice– If you do not already have a registered domain name, such as, you will need to create and register one with a registrar of your choice. You can typically register a domain for a small yearly fee. For procedural information about registering a domain name, see the web site of the registrar

Amazon S3– You will use Amazon S3 to create buckets, upload a sample website page, configure permissions so everyone can see the content, and then configure the buckets for website hosting. In this example, because you want to allow requests for both and, you will create two buckets; however, you will host content in only one bucket. You will configure the other Amazon S3 bucket to redirect requests to the bucket that hosts the content.

Amazon Route 53– You will configure Amazon Route 53 as your DNS provider. You will create a hosted zone in Amazon Route 53 for your domain and configure applicable DNS records. If you are switching from an existing DNS provider, you will need to ensure that you have transferred all of the DNS records for your domain.

As you walk through this example, a basic familiarity with domains, Domain Name System (DNS), CNAME records, and A records would be helpful. A detailed explanation of these concepts is beyond the scope of this guide, but your domain registrar should provide any basic information that you need.

In this step, we use Amazon Route 53, however most registrars can be used to define a CNAME record pointing to an Amazon S3 bucket.


All the steps in this example use as a domain name. You will need to replace this domain name with the one you registered.

Step 1: Register a Domain

If you already have a registered domain, you can skip this step. If you are new to hosting a website, your first step is to register a domain, such as, with a registrar of your choice.  

After you have chosen a registrar, you will register your domain name according to the instructions at the registrar’s website. For a list of registrar web sites that you can use to register your domain name, see Information for Registrars and Registrants at the website.

When you have a registered domain name, your next task is to create and configure Amazon S3 buckets for website hosting and to upload your website content.

Step 2: Create and Configure Buckets and Upload Data

In this example, to support requests from both the root domain such as and subdomain such as, you will create two buckets. One bucket will contain the content and you will configure the other bucket to redirect requests. You perform the following tasks in Amazon S3 console to create and configure your website:

  1. Create two buckets.

  2. Configure these buckets for website hosting.

  3. Test the Amazon S3 provided bucket website endpoint.

Step 2.1: Create Two Buckets

The bucket names must match the names of the website that you are hosting. For example, to host your website on Amazon S3, you would create a bucket named To host a website under, you would name the bucket In this example, your website will support requests from both and

In this step, you will sign in to the Amazon S3 console with your AWS account credentials and create the following two buckets.




To create the buckets for this example, follow these steps. As you walk through this example, substitute the domain name that you registered for

  1. Sign in to the AWS Management Console and open the Amazon S3 console at

  2. Create two buckets that match your domain name and subdomain. For instance, and

    For step-by-step instructions, see How Do I Create an S3 Bucket? in the Amazon Simple Storage Service Console User Guide.


    Like domains, subdomains must have their own Amazon S3 buckets, and the buckets must share the exact names as the subdomains. In this example, we are creating the subdomain, so we need to have an Amazon S3 bucket named as well.

  3. Upload your website data to the bucket.

    You will host your content out of the root domain bucket (, and you will redirect requests for to the root domain bucket. Note that you can store content in either bucket. For this example you will host content in bucket. The content can be text files, family photos, videos—whatever you want. If you have not yet created a website, then you only need one file for this example. You can upload any file. For example, you can create a file using the following HTML and upload it the bucket. The file name of the home page of a website is typically index.html, but you can give it any name. In a later step, you will provide this file name as the index document name for your website.

    <html xmlns="" > <head> <title>My Website Home Page</title> </head> <body> <h1>Welcome to my website</h1> <p>Now hosted on Amazon S3!</p> </body> </html>

    For step-by-step instructions, see How Do I Upload an Object to an S3 Bucket? in the Amazon Simple Storage Service Console User Guide.

  4. Configure permissions for your objects to make them publicly accessible.

    Attach the following bucket policy to the bucket substituting the name of your bucket for For step-by-step instructions to attach a bucket policy, see How Do I Add an S3 Bucket Policy? in the Amazon Simple Storage Service Console User Guide.

    { "Version":"2012-10-17", "Statement":[{ "Sid":"PublicReadGetObject", "Effect":"Allow", "Principal": "*", "Action":["s3:GetObject"], "Resource":["*" ] } ] }

    You now have two buckets, and, and you have uploaded your website content to the bucket. In the next step, you will configure to redirect requests to your bucket. By redirecting requests you can maintain only one copy of your website content and both visitors who specify “www” in their browsers and visitors that only specify the root domain will both be routed to the same website content in your bucket. 

Step 2.2: Configure Buckets for Website Hosting

When you configure a bucket for website hosting, you can access the website using the Amazon S3 assigned bucket website endpoint.

In this step, you will configure both buckets for website hosting. First, you will configure as a website and then you'll configure to redirect all requests to the bucket.

To configure bucket for website hosting

  1. Sign in to the AWS Management Console and open the Amazon S3 console at

  2. In the Bucket name list, choose the name of the bucket that you want to enable static website hosting for.

  3. Choose Properties.

  4. Choose Static website hosting.

  5. Configure bucket for website hosting. In the Index Document box, type the name that you gave your index page.

  6. Choose Save.

  7. To test the website, enter the Endpoint URL in your browser. Your browser will display the index document page.

Now that you have configured your bucket for website hosting, you will configure the bucket to redirect all requests for to

To redirect requests from to

  1. In the Amazon S3 console, in the Buckets list, choose your bucket (, in this example).

  2. Choose Properties.

  3. Choose Static website hosting.

  4. Choose Redirect requests. In the Target bucket or domain box, type

  5. To test the website, enter the Endpoint URL in your browser. Your request will be redirected and the browser will display the index document for

You have now successfully redirected requests from one bucket to another, and the following Amazon S3 bucket website endpoints are accessible to any internet user:

Now you will do additional configuration to serve requests from the domain you registered in the preceding step. For example, if you registered a domain, you want to serve requests from the following URLs :

In the next step, we will use Amazon Route 53 to enable customers to use the URLs above to navigate to your site.

Step 3: Create and Configure Amazon Route 53 Hosted Zone

Now you will configure Amazon Route 53 as your Domain Name System (DNS) provider. You must use Amazon Route 53 if you want to serve content from your root domain, such as You will create a hosted zone, which holds the DNS records associated with your domain:

  • An alias record that maps the domain to the bucket. This is the bucket that you configured as a website endpoint in step 2.2.

  • Another alias record that maps the subdomain to the bucket. You configured this bucket to redirect requests to the bucket in step 2.2.

Step 3.1: Create a Hosted Zone for Your Domain

Go to the Amazon Route 53 console at and then create a hosted zone for your domain. For instructions, go to Creating a Hosted Zone in the

The following example shows the hosted zone created for the domain. Write down the Amazon Route 53 name servers (NS) for this domain. You will need them later.

Step 3.2: Add Alias Records for and

The alias records that you add to the hosted zone for your domain will map and to the corresponding Amazon S3 buckets. Instead of using IP addresses, the alias records use the Amazon S3 website endpoints. Amazon Route 53 maintains a mapping between the alias records and the IP addresses where the Amazon S3 buckets reside.

For step-by-step instructions, see Creating Resource Record Sets by Using the Amazon Route 53 Console in the Amazon Route 53 Developer Guide.

The following screenshot shows the alias record for as an illustration. You will also need to create an alias record for

To enable this hosted zone, you must use Amazon Route 53 as the DNS server for your domain Before you switch, if you are moving an existing website to Amazon S3, you must transfer DNS records associated with your domain to the hosted zone that you created in Amazon Route 53 for your domain. If you are creating a new website, you can go directly to step 4.


Creating, changing, and deleting resource record sets take time to propagate to the Route 53 DNS servers. Changes generally propagate to all Route 53 name servers in a couple of minutes. In rare circumstances, propagation can take up to 30 minutes.

Step 3.3: Transfer Other DNS Records from Your Current DNS Provider to Amazon Route 53

Before you switch to Amazon Route 53 as your DNS provider, you must transfer any remaining DNS records from your current DNS provider, including MX records, CNAME records, and A records, to Amazon Route 53. You don't need to transfer the following records:

  • NS records– Instead of transferring these, you replace their values with the name server values that are provided by Amazon Route 53.

  • SOA record– Amazon Route 53 provides this record in the hosted zone with a default value.

Migrating required DNS records is a critical step to ensure the continued availability of all the existing services hosted under the domain name.

Step 4: Switch to Amazon Route 53 as Your DNS Provider

To switch to Amazon Route 53 as your DNS provider, you must go to your current DNS provider and update the name server (NS) record to use the name servers in your delegation set in Amazon Route 53.

Go to your DNS provider site and update the NS record with the delegation set values of the hosted zone as shown in the following Amazon Route 53 console screenshot. For more information, go to Updating Your DNS Service's Name Server Records in Amazon Route 53 Developer Guide.

When the transfer to Amazon Route 53 is complete, there are tools that you can use to verify the name server for your domain has indeed changed. On a Linux computer, you can use the dig DNS lookup utility. For example, this dig command:

dig +recurse +trace any

returns the following output (only partial output is shown). The output shows the same four name servers the name servers on Amazon Route 53 hosted zone you created for domain.

... 172800 IN NS 172800 IN NS 172800 IN NS 172800 IN NS 300 IN CNAME ...

Step 5: Testing

To verify that the website is working correctly, in your browser, try the following URLs:

  • - Displays the index document in the bucket.

  • Redirects your request to

In some cases, you may need to clear the cache of your web browser to see the expected behavior.