Tutorial: Configuring a static website using a custom domain registered with Route 53

To create your buckets for website hosting

The following instructions provide an overview of how to create your buckets for website hosting. For detailed, step-by-step instructions on creating a bucket, see Creating a bucket.

1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

2. Create your root domain bucket:

   1. Choose Create bucket.

   2. Enter the Bucket name (for example, example.com).

   3. Choose the Region where you want to create the bucket.

      Choose a Region that is geographically close to you to minimize latency and costs, or to address regulatory requirements. The Region that you choose determines your Amazon S3 website endpoint. For more information, see Website endpoints.

   4. To accept the default settings and create the bucket, choose Create.

3. Create your subdomain bucket:

   1. Choose Create bucket.

   2. Enter the Bucket name (for example, www.example.com).

   3. Choose the Region where you want to create the bucket.

      Choose a Region that is geographically close to you to minimize latency and costs, or to address regulatory requirements. The Region that you choose determines your Amazon S3 website endpoint. For more information, see Website endpoints.

   4. To accept the default settings and create the bucket, choose Create.

To enable static website hosting

1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

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

3. Choose Properties.

4. Under Static website hosting, choose Edit.

5. Choose Use this bucket to host a website.

6. Under Static website hosting, choose Enable.

7. In Index document, enter the file name of the index document, typically index.html.

   The index document name is case sensitive and must exactly match the file name of the HTML index document that you plan to upload to your S3 bucket. When you configure a bucket for website hosting, you must specify an index document. Amazon S3 returns this index document when requests are made to the root domain or any of the subfolders. For more information, see Configuring an index document.

8. To provide your own custom error document for 4XX class errors, in Error document, enter the custom error document file name.

   The error document name is case sensitive and must exactly match the file name of the HTML error document that you plan to upload to your S3 bucket. If you don't specify a custom error document and an error occurs, Amazon S3 returns a default HTML error document. For more information, see Configuring a custom error document.

9. (Optional) If you want to specify advanced redirection rules, in Redirection rules, enter JSON to describe the rules.

   For example, you can conditionally route requests according to specific object key names or prefixes in the request. For more information, see Configure redirection rules to use advanced conditional redirects.

10. Choose Save changes.

    Amazon S3 enables static website hosting for your bucket. At the bottom of the page, under Static website hosting, you see the website endpoint for your bucket.

11. Under Static website hosting, note the Endpoint.

    The Endpoint is the Amazon S3 website endpoint for your bucket. After you finish configuring your bucket as a static website, you can use this endpoint to test your website.

To configure a redirect request

1. On the Amazon S3 console, in the Buckets list, choose your subdomain bucket name (www.example.com in this example).

2. Choose Properties.

3. Under Static website hosting, choose Edit.

4. Choose Redirect requests for an object.

5. In the Target bucket box, enter your root domain, for example, example.com.

6. For Protocol, choose http.

7. Choose Save changes.

To enable server access logging for your root domain bucket

1. Open the Amazon S3 console at https://console.aws.amazon.com/s3/.

2. In the same Region where you created the bucket that is configured as a static website, create a bucket for logging, for example logs.example.com.

3. Create a folder for the server access logging log files (for example, logs).

4. (Optional) If you want to use CloudFront to improve your website performance, create a folder for the CloudFront log files (for example, cdn).

   Important

   When you create or update a distribution and enable CloudFront logging, CloudFront updates the bucket access control list (ACL) to give the awslogsdelivery account FULL_CONTROL permissions to write logs to your bucket. For more information, see Permissions required to configure standard logging and to access your log files in the Amazon CloudFront Developer Guide. If the bucket that stores the logs uses the Bucket owner enforced setting for S3 Object Ownership to disable ACLs, CloudFront cannot write logs to the bucket. For more information, see Controlling ownership of objects and disabling ACLs for your bucket.

5. In the Buckets list, choose your root domain bucket.

6. Choose Properties.

7. Under Server access logging, choose Edit.

8. Choose Enable.

9. Under the Target bucket, choose the bucket and folder destination for the server access logs:

   • Browse to the folder and bucket location:

     1. Choose Browse S3.

     2. Choose the bucket name, and then choose the logs folder.

     3. Choose Choose path.

   • Enter the S3 bucket path, for example, s3://logs.example.com/logs/.

10. Choose Save changes.

    In your log bucket, you can now access your logs. Amazon S3 writes website access logs to your log bucket every 2 hours.

To configure the index document

1. Create an index.html file.

   If you don't have an index.html file, you can use the following HTML to create one:

   <html xmlns="http://www.w3.org/1999/xhtml" >
   <head>
       <title>My Website Home Page</title>
   </head>
   <body>
     <h1>Welcome to my website</h1>
     <p>Now hosted on Amazon S3!</p>
   </body>
   </html>

2. Save the index file locally.

   The index document file name must exactly match the index document name that you enter in the Static website hosting dialog box. The index document name is case sensitive. For example, if you enter index.html for the Index document name in the Static website hosting dialog box, your index document file name must also be index.html and not Index.html.

3. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

4. In the Buckets list, choose the name of the bucket that you want to use to host a static website.

5. Enable static website hosting for your bucket, and enter the exact name of your index document (for example, index.html). For more information, see Enabling website hosting.

   After enabling static website hosting, proceed to step 6.

6. To upload the index document to your bucket, do one of the following:

   • Drag and drop the index file into the console bucket listing.

   • Choose Upload, and follow the prompts to choose and upload the index file.

   For step-by-step instructions, see Uploading objects.

7. (Optional) Upload other website content to your bucket.

To configure an error document

1. Create an error document, for example 404.html.

2. Save the error document file locally.

   The error document name is case sensitive and must exactly match the name that you enter when you enable static website hosting. For example, if you enter 404.html for the Error document name in the Static website hosting dialog box, your error document file name must also be 404.html.

3. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

4. In the Buckets list, choose the name of the bucket that you want to use to host a static website.

5. Enable static website hosting for your bucket, and enter the exact name of your error document (for example, 404.html). For more information, see Enabling website hosting and Configuring a custom error document.

   After enabling static website hosting, proceed to step 6.

6. To upload the error document to your bucket, do one of the following:

   • Drag and drop the error document file into the console bucket listing.

   • Choose Upload, and follow the prompts to choose and upload the index file.

   For step-by-step instructions, see Uploading objects.

1. Open the Amazon S3 console at https://console.aws.amazon.com/s3/.

2. Choose the name of the bucket that you have configured as a static website.

3. Choose Permissions.

4. Under Block public access (bucket settings), choose Edit.

5. Clear Block all public access, and choose Save changes.

   

   Amazon S3 turns off the Block Public Access settings for your bucket. To create a public static website, you might also have to edit the Block Public Access settings for your account before adding a bucket policy. If the Block Public Access settings for your account are currently turned on, you see a note under Block public access (bucket settings).

1. Under Buckets, choose the name of your bucket.

2. Choose Permissions.

3. Under Bucket Policy, choose Edit.

4. To grant public read access for your website, copy the following bucket policy, and paste it in the Bucket policy editor.

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

5. Update the Resource to your bucket name.

   In the preceding example bucket policy, Bucket-Name is a placeholder for the bucket name. To use this bucket policy with your own bucket, you must update this name to match your bucket name.

6. Choose Save changes.

   A message appears indicating that the bucket policy has been successfully added.

   If you see an error that says Policy has invalid resource, confirm that the bucket name in the bucket policy matches your bucket name. For information about adding a bucket policy, see How do I add an S3 bucket policy?

   If you get an error message and cannot save the bucket policy, check your account and bucket Block Public Access settings to confirm that you allow public access to the bucket.

1. Under Buckets, choose the name of your bucket.

2. Choose Properties.

3. At the bottom of the page, under Static website hosting, choose your Bucket website endpoint.

   Your index document opens in a separate browser window.