Lifecycle Configuration Elements

Metadata

ID

Definition:

Rule ID, which uniquely identifies a rule.

Value range:

The value is a string ranging from 0 (exclusive) to 255 characters. It can contain only uppercase or lowercase letters, digits, periods (.), underscores (_), and hyphens (-).

Default value:

If the ID element is not used or is left blank, OBS automatically assigns a unique ID to the rule.

Status

Definition:

It indicates whether the rule is enabled or disabled. If the rule is disabled, OBS does not perform any actions defined in the rule.

Value range:

• Enabled: The rule is enabled.
• Disabled: The rule is disabled.

Default value:

N/A

Filters

Prefix

Definition:

Object name prefix, which identifies the objects to which the lifecycle rule applies

If you leave the Prefix element blank, the rule applies to all objects in the bucket.

Constraints:

• Each lifecycle rule must have only one prefix. If no prefix is required for filtering, use <Prefix></Prefix> to leave the Prefix element blank.
• If you specify only the Prefix element and no Tag element, the parent node Filter is not required. In the example below, only the texta/ prefix is specified and no Tag elements are specified, so the Filter element is not required.

  1 2 3 4 5 6 7 8 9 10 11

  <LifecycleConfiguration> <Rule> <ID>sample-rule</ID> <Prefix>texta/</Prefix> <Status>Enabled</Status> <Transition> <Days>100</Days> <StorageClass>COLD</StorageClass> </Transition> </Rule> </LifecycleConfiguration>

Value range:

The value is a string ranging from 0 to 1024 characters.

Default value:

If this element is not specified, it is left blank by default.

Tag

Definition:

Object tag, which identifies the objects to which the lifecycle rule applies.

Constraints:

• Object tags cannot be used as filters for deleting fragments or deleting expired delete markers.
• A lifecycle rule allows for zero or up to 10 object tags.
• If there are multiple tags specified in a rule, each tag key must be unique.
• A tag key:

1. Can be 128 characters long at most. It consists of letters, digits, and spaces representable in UTF-8, and the following special characters: _ . : = + - @.
2. Must be case sensitive. If there are multiple tags, each tag key must be unique.
3. Cannot be left blank.

• A tag value:

1. Can be 255 characters long at most. It consists of letters, digits, and spaces representable in UTF-8, and the following special characters: _ . : / = + - @.
2. Must be case sensitive.
3. Can be left blank.

In the example below, objects with the key1/value1 tag will be deleted 120 days after the last update.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

<LifecycleConfiguration>  
    <Rule>
        <ID>sample-rule</ID>  
        <Status>Enabled</Status>
        <Filter>
            <Tag>
                <Key>key1</Key>
                <Value>value1</Value>
            </Tag>
        </Filter>                
        <Expiration>
            <Days>120</Days>
        </Expiration>
    </Rule>
</LifecycleConfiguration>

Default value:

If this element is not specified, it is left blank by default.

Combination of Prefix and Tag

You can filter objects by a combination of prefix and object tags. In this case, you need to use a logical And to combine the filters. A logical And must contain at least two filter conditions. Prefix is mandatory and only one prefix can be configured. Tag is optional and up to 10 tags can be configured.

In the example below, objects with the key1/value1 tag and the texta/ prefix will be deleted 120 days after the last modification.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18

<LifecycleConfiguration>
    <Rule>
        <ID>sample-rule</ID>  
        <Status>Enabled</Status>
        <Filter>
            <And>
                <Prefix>texta/</Prefix>
                <Tag>
                    <Key>key1</Key>
                    <Value>value1</Value>
                </Tag>
            </And>
        </Filter>
        <Expiration>
            <Days>120</Days>
        </Expiration>
    </Rule>
</LifecycleConfiguration>

Expiration

Used to delete objects

Days

(Use only one of the Days, Date, and ExpiredObjectDeleteMarker elements.)

Definition:

The number of days since the last object update, after which eligible objects will be expired and then deleted

Constraints:

• Days applies only to the current version of an object.
• For the same object, the time specified for Expiration must be later than that for Transition.

Value range:

A positive integer, in days

Default value:

N/A

Date

(Use only one of the Days, Date, and ExpiredObjectDeleteMarker elements.)

Definition:

The date, before which objects were last modified will be expired and then deleted

Constraints:

• Date applies only to the current version of an object.
• The date must be compliant with ISO 8601 and its time must be 00:00:00 in UTC. If Date is set to 2018-01-01T00:00:00.000Z, objects whose last modification time is earlier than 2018-01-01T00:00:00.000Z will be deleted.
• For the same object, the time specified for Expiration must be later than that for Transition.
• OBS Console and OBS Browser+ do not support the deletion of objects on a specified date.

Default value:

N/A

Used to remove expired delete markers

ExpiredObjectDeleteMarker

(Use only one of the Days, Date, and ExpiredObjectDeleteMarker elements.)

Definition:

Whether to remove expired delete markers

Constraints:

Object tags cannot be used as filters.

Value range:

• true: Expired delete markers are removed.
• false: Expired delete markers are not removed.

Default value:

N/A

Transition

Used to transition objects between storage classes

Days

(Use either Days or Date.)

Definition:

The number of days since the last object update, after which eligible objects will be transitioned to another storage class

Constraints:

Days applies only to the current version of an object.

Value range:

Unit: day

• If only one transition is configured, the time should be at least one day after the update.
• If multiple transitions are configured, the transition to the Deep Archive storage class must be later than the transition to Archive, and the transition to Archive must be later than the transition to Infrequent Access.

Default value:

N/A

Date

(Use either Days or Date.)

Definition:

The date, before which objects were last modified will be transitioned to another storage class

Constraints:

• Date applies only to the current version of an object.
• The date must be compliant with ISO 8601 and its time must be 00:00:00 in UTC. If Date is set to 2018-01-01T00:00:00.000Z, objects whose last modification time is earlier than 2018-01-01T00:00:00.000Z will be transitioned to another storage class.
• If multiple transitions are configured, the transition to the Deep Archive storage class must be later than the transition to Archive, and the transition to Archive must be later than the transition to Infrequent Access.
• OBS Console and OBS Browser+ do not support the transition of objects on a specified date.

Default value:

N/A

StorageClass

Definition:

New storage class eligible objects will be transitioned to

Value range:

• WARM: the Infrequent Access storage class
• COLD: the Archive storage class
• DEEP_ARCHIVE: the Deep Archive storage class

Default value:

N/A

AbortIncompleteMultipartUpload

Used to delete fragments

DaysAfterInitiation

Definition:

The number of days since fragment generation, after which fragments will be expired and then deleted

Constraints:

Object tags cannot be used as filters.

Value range:

A positive integer, in days

Default value:

N/A

NoncurrentVersionExpiration

Used to delete historical object versions

NoncurrentDays

Definition:

The number of days since the objects became noncurrent, after which noncurrent object versions will be deleted

Constraints:

• NoncurrentDays only applies to historical object versions.
• NoncurrentDays can only be used for buckets that have versioning enabled or suspended.
• For the same historical version of an object, the time specified for Expiration must be later than that for Transition.

Value range:

A positive integer, in days

Default value:

N/A

NoncurrentVersionTransition

Used to transition noncurrent versions

NoncurrentDays

Definition:

The number of days since the objects became noncurrent, after which noncurrent object versions will be transitioned to another storage class

Constraints:

• NoncurrentDays only applies to historical object versions.
• NoncurrentDays can only be used for buckets that have versioning enabled or suspended.

Value range:

Unit: day

• If only one transition is involved, the time should be at least one day after the update.
• If multiple transitions are involved, the latter transition should be at least one day later than the former transition.
• If multiple transitions are configured, the transition to the Deep Archive storage class must be later than the transition to Archive, and the transition to Archive must be later than the transition to Infrequent Access.

Default value:

N/A

StorageClass

Definition:

New storage class eligible historical object versions will be transitioned to

Value range:

• WARM: the Infrequent Access storage class
• COLD: the Archive storage class
• DEEP_ARCHIVE: the Deep Archive storage class

Default value:

N/A