PUT Bucket lifecycle

Description

COS allows users to manage the lifecycle of Objects in a Bucket. A lifecycle configuration contains one or more rule sets that will be applied to a set of object rules (where each rule defines an action for COS).
There are two types of operations:

• Conversion Defines when the object is converted to another storage class. For example, you can choose to convert an object to a low-frequency storage (STANDARD_IA for infrequent access) storage class 30 days after it is created. It also supports the sinking of data to archive storage (Archive, which is cheaper and currently only for Mainland China regions). For specific parameters, see the Transition item in the request example description.
• Expiration:Specifies the expiration time of the Object. COS will automatically delete expired Objects for the user.

Notes

PUT Bucket lifecycle is used to create a new lifecycle configuration for Bucket. If the Bucket has been configured with a lifetime, using this interface to create a new configuration will overwrite the original configuration.

Request

Grammar example:

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

Lifecycle configuration in the request body

Authorization: Auth String (see Request Signature for details)

Request line

PUT /?lifecycle HTTP/1.1

The API interface accepts PUT requests.

Request header

Public header

The implementation of this request operation uses the public request header. For details on the public request header, see the Common Request Header section.

Non-public header

Required header
The implementation of this request operation uses the following mandatory headers:

Request body

The specific node content of the request body requested by the API 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 content is described as follows:

Response

Response example:

HTTP/1.1 200 OK
Content-Type: application/xml
Date: Sat, 05 Aug 2017 07:13:50 GMT
Content-Length: 0
Server: tencent-cos
X-cos-request-id: NTk4NTcwMDNfMjQ4OGY3MGFfNDI0Y181

Response header

Public response header

The response uses a common response header. See the Public Response Header section for details on the public response header.

Unique response header

There is no special response header for this response.

Response body

The response body returns empty.

Error Codes

The following describes some of the common mistakes and the special circumstances of this request may occur:

Note: The specific cause of the error can be checked by referring to the returned message.
For more information on COS error codes, or a list of all product errors, please see the Error Codes documentation.

actual case

request

PUT /?lifecycle HTTP/1.1
Host:lifecycletest-73196696.cos.ap-beijing.myqcloud.com
Date: Wed, 16 Aug 2017 11:59:33 GMT
Authorization:q-sign-algorithm=sha1&q-ak=AKIDZfbOAo7cllgPvF9cXFrJD0a1ICvR98JM&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
Server: tencent-cos
X-cos-request-id: NTk5NDMzYTRfMjQ4OGY3Xzc3NGRfMWY=