Release Date: 2006-09-14
Latest WSDL/API Version: 2006-03-01(updated)
|Server access logging (beta) ||You can now configure any Amazon S3 bucket that you own to create access log records for the requests made against it. An access log record contains details about the request such as the request type, the resource the request worked worked with, and the time and date that the request was processed. Server access logs provide object- and request-level usage information that has been requested by the Amazon S3 developer community. |
The server access logging feature is beta functionality that is subject to change in future releases. The Amazon S3 team welcomes your feedback on the Amazon S3 Developer Forums. There are no additional fees for use of server access logging.
For more information, see the Server Access Logging section of the documentation.
|Sample Code Update ||The s3curl.pl sample program has been updated for compatibility with the server access logging feature. |
|Documentation improvements ||Guidance on caching of Amazon S3 IP addresses has been added in the DNS Considerations section of the documentation. The discussion of bucket listing functionality has been clarified to acknowledge that for a short period of time after deleting a bucket, the operation to list all your buckets may continue returning the bucket you deleted, even though it no longer exists. |
|100-Continue ||The HTTP 100-Continue reply sent by S3 (as described in RFC 2616, section 8.2.3.) is unconditional, and therefore not very useful. |
|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. |
|Uploads between 2 GB and 4 GB in size fail ||A load balancer bug causes the connection to close whenever an upload request with content-length between 2 GB and 4 GB is received. Amazon has received a fix for the issue from the load balancer vendor, and is in the process of testing the fix. |
|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.|