|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
When you configure a bucket for website hosting, the website is available via the region-specific website endpoint. Website endpoints are different from the endpoints where you send REST API requests. For more information about the endpoints, see Request Endpoints.
The general form of an Amazon S3 website endpoint is as follows:
For example, if your bucket is named
example-bucket and it resides in the
US Standard region, the website is available at the following Amazon S3 website
The following table lists Amazon S3 regions and the corresponding website endpoints.
|US West (Oregon) Region||
|US West (Northern California) Region||
|EU (Ireland) Region||
|Asia Pacific (Singapore) Region||
|Asia Pacific (Sydney) Region||
|Asia Pacific (Tokyo) Region||
|South America (Sao Paulo) Region||
In order for your customers to access content at the website endpoint, you must make all your content publicly readable. To do so, you can use a bucket policy or an ACL on an object to grant the necessary permissions.
Requester Pays buckets or DevPay buckets do not allow access through the
website endpoint. Any request to such a bucket will receive a
Denied response. For more information, see Requester Pays Buckets.
If you have a registered domain, you can add a DNS CNAME entry to point to the Amazon S3
website endpoint. For example, if you have registered domain,
www.example-bucket.com, you could create a bucket
www.example-bucket.com, and add a DNS CNAME record that points to
http://www.example-bucket.com will be routed to
www.example-bucket.com.s3-website-<region>.amazonaws.com. For more
information, see Virtual Hosting of Buckets.
The website endpoint is optimized for access from a web browser. The following table describes the key differences between the Amazon REST API endpoint and the website endpoint.
|Key Difference||REST API Endpoint||Website Endpoint|
Supports all bucket and object operations
|Supports only GET and HEAD requests on objects.|
|Responses to GET and HEAD requests at the root of a bucket||Returns a list of the object keys in the bucket.||Returns the index document that is specified in the website configuration.|
|Error message handling||
Returns an XML-formatted error response.
|Returns an HTML document.|
Supports both public and private content.
|Supports only publicly readable content.|
|Supports both object-level and bucket-level redirects.|