This topic provides answers to frequently asked questions about lifecycle management.
Is there a limit to the minimum storage period of objects if I set lifecycle rules to convert the storage class of objects or delete expired objects?
If you set a lifecycle rule to convert the storage class of an object from Standard to IA, Archive, or Cold Archive, from IA to Archiveor Cold Archive, or from Archive to Cold Archive, there are no limits to the minimum storage period of the object. However, if you set a lifecycle rule to delete expired objects, there is a minimum storage period for expired objects. The minimum storage period of expired objects to be deleted is determined by the storage class of the objects at the time of deletion. The minimum storage period is 30 days for IA objects and 60 days for Archive objects.
The minimum storage period of an expired object to be deleted begins when the object was created and ends when the object is scheduled to be deleted. If the object is modified by an API operation such as CopyObject or AppendObject during this period, the minimum storage period begins when the object was last modified.
What is the billing logic for the number of requests?
- If you set a lifecycle rule to convert the storage class of 1,000 Standard objects to Archive, 1,000 POST requests are generated.
- If you set a lifecycle rule to delete 1,000 expired objects, 1,000 Delete requests are generated.
For more information about the billing standards, see Billing items and methods.
Does OSS record when object storage classes are converted and expired objects are deleted based on lifecycle rules?
- CommitTransition: indicates that the lifecycle rule is set to convert the storage class of an object.
- ExpireObject: indicates that the lifecycle rule is set to delete an expired object.
- Sync Request
lifecycle: indicates the operation to be performed based on the lifecycle rule.