The expiration lifecycle policy sets an expiration date on the objects within a bucket.
A set of rules is applied to this policy that define actions across groups of objects. These rules can apply to current versions, non-current versions, incomplete multi-part uploads, and expired delete markers.
Each policy can contain up to 1,000 rules. Additionally, each rule contains filters (such as prefixes and tags), as well as actions.
Note: Actions are applied as to your expiration lifecycle policy as rules and can be implemented from the Add rule page of a given bucket.
Actions apply to all objects in the bucket and are specific to the expiration lifecycle policy. They can be added as individually set rules and do not require tags or a prefix. Currently, the following four expiration actions are supported:
- Current versions: Permanenetly deletes an object after a set number of days from object creation, or on a specific date. The default is 365 days.
- Non-current versions: Permanently deletes an object after a set number of days from having been made a previous version, or on a specific date. The default is 30 days.
- Incomplete multi-part uploads: Removes partial MPU uploads if they are not successfully completed within a set number of days.
- Expired delete markers: Retains an expired delete marker in the event that all previous versions of an object expire after the deletion of a versioned object. The default is 7 days.Important: The Expired delete markers policy cannot be set if the Current versions policy is enabled.