New Features
| Feature | Description |
|---|---|
EU Location Constraint |
Amazon S3 now supports location constraints, which allow you to specify where in the world to store data for a bucket and provides a new API to retrieve the location constraint for an existing bucket. For more information, refer to the Amazon S3 Developer Guide. |
New Redirect Requirement |
Programs that make requests against buckets created using the new For more information, refer to the Amazon S3 Developer Guide. |
100-Continue |
Amazon S3 now supports 100-Continue. For PUT operations, this helps you avoid sending the message body if the message is rejected based on the headers (e.g., authentication failure or redirect). |
Known Issues
Configuring HTTP headers using SOAP |
With the exception of the Content-Type header, you cannot add HTTP headers to objects using the SOAP API. |
ETags |
S3 ETags are currently derived from a hash of the object data. According to section 13.3.3 of RFC 2616, this is a weak reference. To be a strong reference, S3 would also have to consider metadata and other headers in the ETag. |
SOAP SSL authentication |
SOAP authentication should only be accepted over SSL but S3 allows SOAP authentication to be performed over non-SSL connections. |
Use of Amazon S3's BitTorrent interface from Amazon EC2 results in data transfer charges |
While regular data transfer between Amazon S3 and Amazon EC2 is free, there is a known issue with the Amazon S3 BitTorrent seeder that results in data transfer charges when accessed from Amazon EC2. The Amazon Web Services team is aware of this issue and will work to address it. In the interim, please be advised that using the Amazon S3 BitTorrent interface from Amazon EC2 will result in data transfer charges. |