Now hosted on Amazon S3!
``` 1. 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`. 1. Sign in to the Amazon Web Services Management Console and open the Amazon S3 console at [https://console.amazonaws.cn/s3/](https://console.amazonaws.cn/s3/). 1. In the left navigation pane, choose **General purpose buckets**. 1. In the buckets list, choose the name of the bucket that you want to use to host a static website. 1. 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](EnableWebsiteHosting.md). After enabling static website hosting, proceed to step 6. 1. 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](upload-objects.md). 1. (Optional) Upload other website content to your bucket. ## Step 7: Upload an error document When you enable static website hosting for your bucket, you enter the name of the error document (for example, **404.html**). After you enable static website hosting for the bucket, you upload an HTML file with this error document name to your bucket. **To configure an error document** 1. Create an error document, for example `404.html`. 1. 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`. 1. Sign in to the Amazon Web Services Management Console and open the Amazon S3 console at [https://console.amazonaws.cn/s3/](https://console.amazonaws.cn/s3/). 1. In the left navigation pane, choose **General purpose buckets**. 1. In the buckets list, choose the name of the bucket that you want to use to host a static website. 1. 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](EnableWebsiteHosting.md) and [Configuring a custom error document](CustomErrorDocSupport.md). After enabling static website hosting, proceed to step 6. 1. 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](upload-objects.md). ## Step 8: Edit S3 Block Public Access settings In this example, you edit block public access settings for the domain bucket (`example.com`) to allow public access. By default, Amazon S3 blocks public access to your account and buckets. If you want to use a bucket to host a static website, you can use these steps to edit your block public access settings. **Warning** Before you complete these steps, review [Blocking public access to your Amazon S3 storage](access-control-block-public-access.md) to ensure that you understand and accept the risks involved with allowing public access. When you turn off block public access settings to make your bucket public, anyone on the internet can access your bucket. We recommend that you block all public access to your buckets. 1. Open the Amazon S3 console at [https://console.amazonaws.cn/s3/](https://console.amazonaws.cn/s3/). 1. Choose the name of the bucket that you have configured as a static website. 1. Choose **Permissions**. 1. Under **Block public access (bucket settings)**, choose **Edit**. 1. Clear **Block *all* public access**, and choose **Save changes**. ![\[The Amazon S3 console, showing the block public access bucket settings.\]](http://docs.amazonaws.cn/en_us/AmazonS3/latest/userguide/images/edit-public-access-clear.png) 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](https://docs.amazonaws.cn/AmazonS3/latest/user-guide/block-public-access-account.html) 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)**. ## Step 9: Attach a bucket policy In this example, you attach a bucket policy to the domain bucket (`example.com`) to allow public read access. You replace the *Bucket-Name* in the example bucket policy with the name of your domain bucket, for example `example.com`. After you edit S3 Block Public Access settings, you can add a bucket policy to grant public read access to your bucket. When you grant public read access, anyone on the internet can access your bucket. **Important** The following policy is an example only and allows full access to the contents of your bucket. Before you proceed with this step, review [How can I secure the files in my Amazon S3 bucket?](https://aws.amazon.com/premiumsupport/knowledge-center/secure-s3-resources/) to ensure that you understand the best practices for securing the files in your S3 bucket and risks involved in granting public access. 1. Under **Buckets**, choose the name of your bucket. 1. Choose **Permissions**. 1. Under **Bucket Policy**, choose **Edit**. 1. 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-cn:s3:::Bucket-Name/*" ] } ] } ``` 1. 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. 1. 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?](https://docs.amazonaws.cn/AmazonS3/latest/user-guide/add-bucket-policy.html) 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. In the next step, you can figure out your website endpoints and test your domain endpoint. ## Step 10: Test your domain endpoint After you configure your domain bucket to host a public website, you can test your endpoint. For more information, see [Website endpoints](WebsiteEndpoints.md). You can only test the endpoint for your domain bucket because your subdomain bucket is set up for website redirect and not static website hosting. **Note** Amazon S3 does not support HTTPS access to the website. If you want to use HTTPS, you can use Amazon CloudFront to serve a static website hosted on Amazon S3. For more information, see [How do I use CloudFront to serve a static website hosted on Amazon S3?](https://www.amazonaws.cn/premiumsupport/knowledge-center/cloudfront-serve-static-website/) and [Requiring HTTPS for communication between viewers and CloudFront](https://docs.amazonaws.cn/AmazonCloudFront/latest/DeveloperGuide/using-https-viewers-to-cloudfront.html). 1. Under **Buckets**, choose the name of your bucket. 1. Choose **Properties**. 1. At the bottom of the page, under **Static website hosting**, choose your **Bucket website endpoint**. Your index document opens in a separate browser window. In the next step, you use Amazon Route 53 to enable customers to use both of your custom URLs to navigate to your site. ## Step 11: Add alias records for your domain and subdomain In this step, you create the alias records that you add to the hosted zone for your domain maps `example.com` and `www.example.com`. 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. You create two alias records, one for your root domain and one for your subdomain. ### Add an alias record for your root domain and subdomain **To add an alias record for your root domain (`example.com`)** 1. Open the Route 53 console at [https://console.amazonaws.cn/route53/](https://console.amazonaws.cn/route53/). **Note** If you don't already use Route 53, see [Step 1: Register a domain](https://docs.amazonaws.cn/Route53/latest/DeveloperGuide/getting-started.html#getting-started-find-domain-name) in the *Amazon Route 53 Developer Guide*. After completing your setup, you can resume the instructions. 1. Choose **Hosted zones**. 1. In the list of hosted zones, choose the name of the hosted zone that matches your domain name. 1. Choose **Create record**. 1. Choose **Switch to wizard**. **Note** If you want to use quick create to create your alias records, see [Configuring Route 53 to route traffic to an S3 Bucket](https://docs.amazonaws.cn/Route53/latest/DeveloperGuide/RoutingToS3Bucket.html#routing-to-s3-bucket-configuring). 1. Choose **Simple routing**, and choose **Next**. 1. Choose **Define simple record**. 1. In **Record name**, accept the default value, which is the name of your hosted zone and your domain. 1. In **Value/Route traffic to**, choose **Alias to S3 website endpoint**. 1. Choose the Region. 1. Choose the S3 bucket. The bucket name should match the name that appears in the **Name** box. In the **Choose S3 bucket** list, the bucket name appears with the Amazon S3 website endpoint for the Region where the bucket was created, for example, `s3-website-us-west-1.amazonaws.com (example.com)`. **Choose S3 bucket** lists a bucket if: + You configured the bucket as a static website. + The bucket name is the same as the name of the record that you're creating. + The current Amazon Web Services account created the bucket. If your bucket does not appear in the **Choose S3 bucket** list, enter the Amazon S3 website endpoint for the Region where the bucket was created, for example, **s3-website-us-west-2.amazonaws.com**. For a complete list of Amazon S3 website endpoints, see [Amazon S3 Website endpoints](https://docs.amazonaws.cn/general/latest/gr/s3.html#s3_website_region_endpoints). For more information about the alias target, see [Value/route traffic to](https://docs.amazonaws.cn/Route53/latest/DeveloperGuide/resource-record-sets-values-alias.html#rrsets-values-alias-alias-target) in the *Amazon Route 53 Developer Guide*. 1. In **Record type**, choose **A ‐ Routes traffic to an IPv4 address and some Amazon resources**. 1. For **Evaluate target health**, choose **No**. 1. Choose **Define simple record**. **To add an alias record for your subdomain (`www.example.com`)** 1. Under **Configure records**, choose **Define simple record**. 1. In **Record name** for your subdomain, type `www`. 1. In **Value/Route traffic to**, choose **Alias to S3 website endpoint**. 1. Choose the Region. 1. Choose the S3 bucket, for example, `s3-website-us-west-2.amazonaws.com (www.example.com)`. If your bucket does not appear in the **Choose S3 bucket** list, enter the Amazon S3 website endpoint for the Region where the bucket was created, for example, **s3-website-us-west-2.amazonaws.com**. For a complete list of Amazon S3 website endpoints, see [Amazon S3 Website endpoints](https://docs.amazonaws.cn/general/latest/gr/s3.html#s3_website_region_endpoints). For more information about the alias target, see [Value/route traffic to](https://docs.amazonaws.cn/Route53/latest/DeveloperGuide/resource-record-sets-values-alias.html#rrsets-values-alias-alias-target) in the *Amazon Route 53 Developer Guide*. 1. In **Record type**, choose **A ‐ Routes traffic to an IPv4 address and some Amazon resources**. 1. For **Evaluate target health**, choose **No**. 1. Choose **Define simple record**. 1. On the **Configure records** page, choose **Create records**. **Note** Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you can route traffic to your Amazon S3 bucket by using the names of the alias records that you created in this procedure. ### Add an alias record for your root domain and subdomain (old Route 53 console) **To add an alias record for your root domain (`example.com`)** The Route 53 console has been redesigned. In the Route 53 console you can temporarily use the old console. If you choose to work with the old Route 53 console, use the procedure below. 1. Open the Route 53 console at [https://console.amazonaws.cn/route53/](https://console.amazonaws.cn/route53/). **Note** If you don't already use Route 53, see [Step 1: Register a domain](https://docs.amazonaws.cn/Route53/latest/DeveloperGuide/getting-started.html#getting-started-find-domain-name) in the *Amazon Route 53 Developer Guide*. After completing your setup, you can resume the instructions. 1. Choose **Hosted Zones**. 1. In the list of hosted zones, choose the name of the hosted zone that matches your domain name. 1. Choose **Create Record Set**. 1. Specify the following values: **Name** Accept the default value, which is the name of your hosted zone and your domain. For the root domain, you don't need to enter any additional information in the **Name** field. **Type** Choose **A – IPv4 address**. **Alias** Choose **Yes**. **Alias Target** In the **S3 website endpoints** section of the list, choose your bucket name. The bucket name should match the name that appears in the **Name** box. In the **Alias Target** listing, the bucket name is followed by the Amazon S3 website endpoint for the Region where the bucket was created, for example `example.com (s3-website-us-west-2.amazonaws.com)`. **Alias Target** lists a bucket if: + You configured the bucket as a static website. + The bucket name is the same as the name of the record that you're creating. + The current Amazon Web Services account created the bucket. If your bucket does not appear in the **Alias Target** listing, enter the Amazon S3 website endpoint for the Region where the bucket was created, for example, `s3-website-us-west-2`. For a complete list of Amazon S3 website endpoints, see [Amazon S3 Website endpoints](https://docs.amazonaws.cn/general/latest/gr/s3.html#s3_website_region_endpoints). For more information about the alias target, see [Value/route traffic to](https://docs.amazonaws.cn/Route53/latest/DeveloperGuide/resource-record-sets-values-alias.html#rrsets-values-alias-alias-target) in the *Amazon Route 53 Developer Guide*. **Routing Policy** Accept the default value of **Simple**. **Evaluate Target Health** Accept the default value of **No**. 1. Choose **Create**. **To add an alias record for your subdomain (`www.example.com`)** 1. In the hosted zone for your root domain (`example.com`), choose **Create Record Set**. 1. Specify the following values: **Name** For the subdomain, enter `www` in the box. **Type** Choose **A – IPv4 address**. **Alias** Choose **Yes**. **Alias Target** In the **S3 website endpoints** section of the list, choose the same bucket name that appears in the **Name** field—for example, `www.example.com (s3-website-us-west-2.amazonaws.com)`. **Routing Policy** Accept the default value of **Simple**. **Evaluate Target Health** Accept the default value of **No**. 1. Choose **Create**. **Note** Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you can route traffic to your Amazon S3 bucket by using the names of the alias records that you created in this procedure. ## Step 12: Test the website Verify that the website and the redirect work correctly. In your browser, enter your URLs. In this example, you can try the following URLs: + **Domain** (`http://example.com`) – Displays the index document in the `example.com` bucket. + **Subdomain** (`http://www.example.com`) – Redirects your request to `http://example.com`. You see the index document in the `example.com` bucket. If your website or redirect links don't work, you can try the following: + **Clear cache** – Clear the cache of your web browser. + **Check name servers** – If your web page and redirect links don't work after you've cleared your cache, you can compare the name servers for your domain and the name servers for your hosted zone. If the name servers don't match, you might need to update your domain name servers to match those listed under your hosted zone. For more information, see [Adding or changing name servers and glue records for a domain](https://docs.amazonaws.cn/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html). After you've successfully tested your root domain and subdomain, you can set up an [Amazon CloudFront](http://www.amazonaws.cn/cloudfront) distribution to improve the performance of your website and provide logs that you can use to review website traffic. For more information, see [Speeding up your website with Amazon CloudFront](website-hosting-cloudfront-walkthrough.md).