Release: Amazon Simple Storage Service on 2010-02-08

Release Notes>Amazon S3>Release: Amazon Simple Storage Service on 2010 02 08
Amazon S3 introduces beta support for object versioning.

Details

Submitted By: GeorgeNickels@AWS
Release Date: February 8, 2010 12:00 AM GMT
Latest Version: 2006-03-01
Latest WSDL: http://doc.s3.amazonaws.com/2006-03-01/AmazonS3.wsdl
Created On: February 9, 2010 1:34 AM GMT
Last Updated: March 16, 2010 11:55 PM GMT

These release notes provide a summary of all New Features, Resolved Issues, and Known Issues in this version of the Amazon Simple Storage Service.

New Features

The following table describes the new feature found in this release.

Feature Description

Object Versioning

This release introduces object Versioning. All objects now have a key and a version ID. If you enable versioning for a bucket, Amazon S3 gives all objects added to a bucket a unique version ID. This feature enables you to have multiple versions of the same object in a bucket and to recover from unintended overwrites and deletions.

 

Known Issues

The following table describes irregular behavior seen in this release..

Issue Description Impact
The CommonPrefixes result element can include keys whose latest version is a delete marker. This issue was resolved on 3/11/2010. When performing a GET Bucket request with a delimiter parameter on a versioning-enabled or versioning-suspended Amazon S3 bucket, the CommonPrefixes result element can include keys whose latest version is a delete marker. This issue does not apply to buckets that have never been enabled for versioning.
x-amz-mfa request header not required when enabling MFA Delete. This issue was resolved on 2/18/2010. When a user attempts to enable MFA Delete, the system does not return an error response if the x-amz-mfa header element is omitted from the PUT /?versioning request. An x-amz-mfa header should be required to enable MFA Delete.
This issue applies to buckets that have been enabled for versioning with MFA Delete.
Incorrect error response for incorrect serial number in x-amz-mfa value. This issue was resolved on 2/18/2010. If a user specifies an incorrect serial number within a request’s <x-amz-mfa> header, Amazon S3 will return a 500 error response. The system should return a 400 error response for requests that contain incorrect serial numbers.
This issue applies to buckets that have been enabled for versioning with MFA Delete.
©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.