Bucket Configuration Options

When creating buckets, you can take advantage of additional Amazon S3 features by attaching the <CreateBucketConfiguration> XML body to a PUT Bucket request. Currently, you can select a location constraint. For more information, see Location Selection.

Buckets created with <CreateBucketConfiguration> are subject to additional restrictions:

Location Selection

You can now choose a location constraint that will affect where objects are stored within Amazon S3. You can currently specify a Europe (EU) location constraint.

Choosing a location is simple; just specify a location constraint when creating a new bucket and all objects placed within that bucket are automatically stored in the same location.

[Note]Note

If you do not specify a location constraint, Amazon S3 automatically selects a location which will be billed at the standard Amazon S3 rates.

Pricing varies based on the specified location constraint. For more information, go to the Amazon S3 portal page.

The SOAP API does not support requests that use CreateBucketConfiguration.

Bucket Access

To access Amazon S3 buckets and objects that were created using CreateBucketConfiguration, you must use the virtual hosted-style request. For example:

http://yourbucket.s3.amazonaws.com/yourobject

You cannot use the path-style request:

http://s3.amazonaws.com/yourbucket/yourobject

If you use the path-style request, you receive a permanent redirect.

Redirection

Amazon supports two types of redirects: temporary and permanent.

Temporary redirects automatically redirect users that do not have DNS information for the requested bucket. This occurs because DNS changes take time to propagate through the Internet. For example, if a user creates a bucket with a location constraint and immediately stores an object in the bucket, information about the bucket might not distribute throughout the Internet. Because the bucket is a subdomain of s3.amazonaws.com, Amazon S3 redirects it to the correct Amazon S3 location.

Permanent redirects redirect users from the path-style request to the virtual hosted-style request format for buckets created using <CreateBucketConfiguration>. Users will be provided with the correct URL, but will not be forwarded to the correct location.