S3 Bucket Lifecycle:Set Bucket Lifecycle

Search (SHIFT+S)

ECS Management API

ECS Object Service API

ECS API Changes

Set Bucket Lifecycle

PUT /?lifecycle

Creates or replaces the lifecycle configuration for the bucket.

URL Format

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

Request Headers

Content-MD5	required	This is the 128-bit MD5 digest of data which is base64 encoded. This is used to verify that the request was not corrupted during transit.
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, either the x-amz-date or the Date header must also be specified 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 owner of the bucket or a user having permission can create or replace the lifecycle configuration for the bucket
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

<LifecycleConfiguration>
   <Rule>
      <ID></ID>
      <Filter>
         <Prefix></Prefix>
         <Tag>
            <Key></Key>
            <Value></Value>
         </Tag>
         <And>
            <Prefix></Prefix>
            <Tag>
               <Key></Key>
               <Value></Value>
            </Tag>
         </And>
      </Filter>
      <Prefix></Prefix>
      <Status></Status>
      <Expiration>
         <Days></Days>
         <Date></Date>
         <ExpiredObjectDeleteMarker></ExpiredObjectDeleteMarker>
      </Expiration>
      <AbortIncompleteMultipartUpload>
         <DaysAfterInitiation></DaysAfterInitiation>
      </AbortIncompleteMultipartUpload>
      <NoncurrentVersionExpiration>
         <NoncurrentDays></NoncurrentDays>
      </NoncurrentVersionExpiration>
      <Transition>
         <Days></Days>
         <StorageClass></StorageClass>
      </Transition>
   </Rule>
</LifecycleConfiguration>

Not Supported

All parameters are required unless otherwise stated.

Field	Description	Type	Notes
LifecycleConfiguration
Rule			0-* Elements
ID	The rule's unique identifier	String	Valid Values: value is less than or equal to 255 characters
Filter
Prefix	Objects having the key prefix, to which the rule should apply	String
Tag
Key		String
Value		String
And
Prefix	Objects having the key prefix, to which the rule should apply	String
Tag			0-* Elements
Key		String
Value		String
Prefix	Objects having the key prefix, to which the rule should apply	String
Status		String
Expiration
Days	Indicates the number of days after the creation of the object when this rule should take effect	String	Valid Values: A non-negative integer value
Date	The date when the rule must be applied	String	Valid Values: value conforming to ISO 8601 format
ExpiredObjectDeleteMarker	Remove delete marker for expired objects	String	Valid Values: value true or false
AbortIncompleteMultipartUpload
DaysAfterInitiation	Indicates the number of days after the initialization of the uploads when abort uploads operation should take effect	String	Valid Values: A non-negative integer value
NoncurrentVersionExpiration
NoncurrentDays		String	Valid Values: A non-negative integer value
Transition
Days	Indicates the number of days after the creation of the object when this rule should take effect	String	Valid Values: A non-negative integer value
StorageClass	Defines the destination storage class for old objects to transit into	String	Valid Values: none TODO: replace with valid storage classes

Response Headers

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

Response Body

Response indicating Success or Failure to set bucket lifecycle.