Document History

Amazon S3 now supports hosting static websites at the root domain. Visitors to your website can access your site from their browser without specifying "www" in the web address (e.g., "example.com"). Many customers already host static websites on Amazon S3 that are accessible from a "www" subdomain (e.g., "www.example.com"). Previously, to support root domain access, you needed to run your own web server to proxy root domain requests from browsers to your website on Amazon S3. Running a web server to proxy requests introduces additional costs, operational burden, and another potential point of failure. Now, you can take advantage of the high availability and durability of Amazon S3 for both "www" and root domain addresses.

For an example walkthrough, go to go to Example: Setting Up a Static Website Using a Custom Domain. For conceputal information, go to Hosting Static Websites on Amazon S3 in the Amazon Simple Storage Service Developer Guide.

Amazon S3 now support a storage option that enables you to utilize Amazon Glacier's low-cost storage service for data archival. To archive objects, you define archival rules identifying objects and a timeline when you want Amazon S3 to archive these objects to Amazon Glacier. You can easily set the rules on a bucket using the Amazon S3 console or programmatically using the Amazon S3 API or AWS SDKs.

To support data archival rules, Amazon S3 lifecycle management API has been updated. For more information, see PUT Bucket lifecycle.

After you archive objects, you must first restore a copy before you can access the data. Amazon S3 offers an new API for you to initiate a restore. For more information, see POST Object restore.

For conceputal information, go to Object Lifecycle Management in the Amazon Simple Storage Service Developer Guide.

For a bucket that is configured as a website, Amazon S3 now supports redirecting a request for an object to another object in the same bucket or to an external URL. You can configure redirect by adding the x-amz-website-redirect-location metadata to the object.

The object upload APIs PUT Object, Initiate Multipart Upload, and POST Object allow you to configure the x-amz-website-redirect-location object metadata.

For conceputal information, go to How to Configure Website Page Redirects in the Amazon Simple Storage Service Developer Guide.

Amazon S3 now supports Multi-Object Delete API that enables you to delete multiple objects in a single request. With this feature, you can remove large numbers of objects from Amazon S3 more quickly than using multiple individual DELETE requests.

For more information about the API see, see Delete Multiple Objects.

For conceptual information about the delete operation, see Deleting Objects.

Server-side encryption support

Amazon S3 now supports server-side encryption. It enables you to request Amazon S3 to encrypt your data at rest, that is, encrypt your object data when Amazon S3 writes your data to disks in its data centers. To request server-side encryption, you must add the x-amz-server-side-encryption header to your request. To learn more about data encryption, go to Using Data Encryption.

Multipart Upload API extended to enable copying objects up to 5 TB

Prior to this release, Amazon S3 API supported copying objects (see PUT Object - Copy) of up to 5 GB in size. To enable copying objects larger than 5 GB, Amazon S3 extends the multipart upload API with a new operation, Upload Part (Copy). You can use this multipart upload operation to copy objects up to 5 TB in size. For conceptual information about multipart upload, go to Uploading Objects Using Multipart Upload. To learn more about the new API, see Upload Part - Copy.

SOAP API calls over HTTP disabled

To increase security, SOAP API calls over HTTP are disabled. Authenticated and anonymous SOAP requests must be sent to Amazon S3 using SSL.

Support for hosting static websites in Amazon S3

Amazon S3 introduces enhanced support for hosting static websites. This includes support for index documents and custom error documents. When using these features, requests to the root of your bucket or a subfolder (e.g., http://mywebsite.com/subfolder) returns your index document instead of the list of objects in your bucket. If an error is encountered, Amazon S3 returns your custom error message instead of an Amazon S3 error message. For API information to configure your bucket as a website, see the following sections:

For conceptual overview, go to Hosting Websites on Amazon S3 in the Amazon Simple Storage Service Developer Guide.

17 February 2011

Response Header API Support

The GET Object REST API now allows you to change the response headers of the REST GET Object request for each request. That is, you can alter object metadata in the response, without altering the object itself. For more information, see GET Object.

14 January 2011

Large Object Support

Amazon S3 has increased the maximum size of an object you can store in an S3 bucket from 5 GB to 5 TB. If you are using the REST API you can upload objects of up to 5 GB size in a single PUT operation. For larger objects, you must use the Multipart Upload REST API to upload objects in parts. For conceptual information, go to Uploading Objects Using Multipart Upload. For multipart upload API information, see Initiate Multipart Upload, Upload Part, Complete Multipart Upload, List Parts, and List Multipart Uploads

9 December 2010

Multipart upload

Multipart upload enables faster, more flexible uploads into Amazon S3. It allows you to upload a single object as a set of parts. For conceptual information, go to Uploading Objects Using Multipart Upload. For multipart upload API information, see Initiate Multipart Upload, Upload Part, Complete Multipart Upload, List Parts, and List Multipart Uploads

10 November 2010