New Features
| Feature | Description |
|---|---|
Copy |
Amazon S3 now supports the beta version of copying objects without downloading and re-uploading them. For more information, refer to the Amazon Simple Storage Service Developer Guide. |
Query String Authentication Support for Amazon DevPay |
Amazon S3 now supports query string authentication for Amazon DevPay. For more information, refer to the Amazon DevPay Developer Guide. |
Known Issues
Browser might override encoding |
POST forms must be UTF-8 encoded. If a user's browser overrides the encoding, this might cause some characters to become scrambled and result in the uploaded data being corrupted. |
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 |
Amazon 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, Amazon 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 Amazon 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. |