Setting the Bucket Lifecycle

Description

COS allows you to manage the lifecycle of objects in buckets through lifecycle configuration, which contains one or more rulesets that will be applied to a set of object rules (where each rule defines an operation in COS).
These operations include the following two types:

• Conversion: Defines the time when an object is converted to another storage type. For example, you can convert an object to the infrequent access storage (STANDARD_IA, suitable for infrequent access) 30 days after creation. The data can also be stored in the archive storage (ARCHIVE, lower costs and available in China). For specific parameters, see the Transition item in the sample request description.
• Expiration: Specifies the expiration time of an object. COS automatically deletes expired objects.

Notes

PUT Bucket lifecycle is used to create a new lifecycle configuration for a Bucket. If a lifecycle configuration has already been set for the bucket, the new configuration created with this API will overwrite the existing one.

Request

Request Example

PUT /?lifecycle HTTP/1.1
Host: <BucketName-APPID>.<Endpoint>
Content-Length: length
Date: GMT Date
Authorization: Auth String 
Content-MD5: MD5

Note:

Authorization: Auth String (See Request Signature for details.)

Request Header

Common Headers

This request uses common request headers. For details, see Public Request Headers.

Non-common Headers

Required headers:
This request is implemented by using the following required headers.

Request Body

The specific node content of the API request body is:

<LifecycleConfiguration>
  <Rule>
    <ID></ID>
    <Filter>
      <Prefix></Prefix>
    </Filter>
    <Status></Status>
    <Transition>
      <Days></Days>
      <StorageClass></StorageClass>
    </Transition>
    <NoncurrentVersionExpiration>
      <NoncurrentDays></NoncurrentDays>
    </NoncurrentVersionExpiration>
  </Rule>
  <Rule>
    <ID></ID>
    <Filter>
      <Prefix></Prefix>
    </Filter>
    <Status></Status>
    <Transition>
      <Days></Days>
      <StorageClass></StorageClass>
    </Transition>
    <NoncurrentVersionTransition>
      <NoncurrentDays></NoncurrentDays>
      <StorageClass></StorageClass>
    </NoncurrentVersionTransition>
  </Rule>
  <Rule>
    <ID></ID>
    <Filter>
      <Prefix></Prefix>
    </Filter>
    <Status></Status>
    <Expiration>
      <ExpiredObjectDeleteMarker></ExpiredObjectDeleteMarker>
    </Expiration>
    <NoncurrentVersionExpiration>
      <NoncurrentDays></NoncurrentDays>
    </NoncurrentVersionExpiration>
  </Rule>
</LifecycleConfiguration>

The specific contents are described as follows:

Response

Response Headers

Common Response Headers

This response uses common response headers. For details, see Common Response Headers.

Special Response Headers

There are no special response headers for this response operation.

Response Body

The response body is empty.

Error Code

The following table describes some special and common errors that may occur with this request. For detailed error causes, check the returned message. For details on error codes related to COS or the complete list of errors for the product, see Error Codes.

Practical Case

Request

PUT /?lifecycle HTTP/1.1
Host:<BucketName-APPID>.<Endpoint>
Date: Wed, 16 Aug 2017 11:59:33 GMT
Authorization:q-sign-algorithm=sha1&q-ak=AKIDxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&q-sign-time=1502855771;1502935771&q-key-time=1502855771;1502935771&q-header-list=content-md5;host&q-url-param-list=lifecycle&q-signature=f3aa2c708cfd8d4d36d658de56973c9cf1c24654
Content-MD5: LcNUuow8OSZMrEDnvndw1Q==
Content-Length: 348
Content-Type: application/x-www-form-urlencoded

<LifecycleConfiguration>
  <Rule>
    <ID>id1</ID>
    <Filter>
       <Prefix>documents/</Prefix>
    </Filter>
    <Status>Enabled</Status>
    <Transition>
      <Days>100</Days>
      <StorageClass>ARCHIVE</StorageClass>
    </Transition>
  </Rule>
  <Rule>
    <ID>id2</ID>
    <Filter>
       <Prefix>logs/</Prefix>
    </Filter>
    <Status>Enabled</Status>
    <Expiration>
      <Days>10</Days>
    </Expiration>
  </Rule>
</LifecycleConfiguration>

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 0
Date: Wed, 16 Aug 2017 11:59:33 GMT
x-cos-request-id: NTk5NDMzYTRfMjQ4OGY3Xzc3NGRfMWY=