• S3 Bucket Versioning

Set Bucket Versioning

Sets the versioning state of an existing bucket. Unless this state has been set, a bucket does not have a versioning state and all objects added to a bucket receive a null version ID.

Versioning state can be set with one of the following values:

• Enabled - enables versioning for the objects in the bucket. The objects being added to the bucket will receive a unique version ID.

• Suspended - disables versioning for the objects in the bucket. Existing versions of an object remain, however, subsequent objects written to the bucket will have a null version ID.

URL Format

Host Style: http://bucketname.ns1.emc.com/?versioning
Path Style: http://ns1.emc.com/bucketname?versioning

Request Headers

x-amz-date	optional	The timestamp of the request added by the requester. Example: Tue, 03 Sept 2013 12:00:00 GMT. If the Authorization header is specified, you must specify either the x-amz-date or the Date header. If both the headers are specified, the value of x-amz-date header is chosen.
Authorization	required	Information needed to authenticate requests.

---

Prerequisites

The following conditions must be met in order to call this operation.

• Only the bucket owner can set it's versioning state.

• BaseUrl used in a host-style request URL should be pre-configured using the ECS Management API or the ECS Portal (for example, emc.com in the URL: bucketname.ns1.emc.com).

• Namespace corresponding to this bucket should exist (for example, ns1)

---

Request Payload

Table XML

<VersioningConfiguration>
   <Status></Status>
</VersioningConfiguration>

Not Supported

---

Response Headers

x-amz-request-id	optional	Request id.
x-amz-id-2	optional	Bucket identifier.

---

Response Body

Response indicating Success or Failure for this operation.