COS supports object-based lifecycle configuration. By sending specified description languages, it can make objects that meet the rules automatically execute some operations under the specified conditions.
Note:
A lifecycle can be set to as long as 3,650 days.
Applicable Scenario
Logging
If you use COS to store log data, you can configure the lifecycle to automatically delete the log data in 2 years.
Support Notes
Supported Operations
- Deletion upon expiration: Set the expiration time of the object so that the object will be automatically deleted after expiration.
Supported Resources
- Specify by prefix: Objects that match the prefix rule will be processed according to the rule.
- Specify by version: non-current objects will be processed according to the rule.
- Specify by delete marker: The lifecycle feature can remove the marker automatically after all historical versions are deleted.
- Specify by incomplete multipart uploads: Process incomplete multipart uploads.
Supported Time Conditions
- Based on number of days: Specify after how many days since an object was last modified that an action will occur.
- Based on date: Specify the date when the action corresponding to the rule will occur.
Notes
Deletion upon Expiration
How It Works
When an object matches the specified lifecycle rule of deletion upon expiration, Converge Cloud will add the object to the asynchronous deletion queue. There may be a certain delay in actual deletion. You can get the current status of the object by performing GET or HEAD Object operation.
Final consistency
If multiple conflicting rules are configured for the same set of objects, the rule that will expire first will be performed first. Deletion upon expiration will be performed before the transition.
Note:
It is strongly recommended that you do not configure conflicting lifecycle rules for the same set of objects in COS, because this may result in different fees.
Cost Considerations
Execution Instructions
For any configurations sent at any time, COS will start executing the operations at 0:00 the next day in local time. Since the operations are executed in an asynchronous queue, for objects uploaded after the rules are set, COS will usually complete the operations by 24:00 the next day.
When an accident occurs or there are too many objects in the bucket, lifecycle execution may fail. For failures due to other reasons, perform the GET or HEAD Object operation to get the current object status.
No billing commitment is provided for the effectiveness of the lifecycle execution, that is, the billing of the object will change when the lifecycle execution is completed.
No Size Limits
COS does not check the size of files and will unconditionally execute the conversion of objects according to the specified rules.