...
A rule contains an expiration action indicating the deletion of an object when the rule applies. The expiration action operates on the current version of an object, either by deleting the object permanently in a non-versioned bucket or creating a delete marker in a versioned bucket.
A time limit is provided in the form of “integral number of days” or “absolute date”.
If an absolute date is provided, any Any object created before that date is subject to expiration if an absolute date is provided.
When an integral number of days is provided, the evaluation of the expiration cut-off for the current version uses the object version’s age, rounding up to midnight UTC. The integral number of days starts from 0 at that time. For historic (non-current) object versions, the date of the next newest object version is used for evaluation, again rounded up to midnight UTC.
In both cases, the policy takes effect at midnight UTC of the specified date.
Policies based on the number of object versions are not yet supported.
Swarm supports
policy.lifecyclepolicy setting at the cluster level that acts as a master switch for the feature.
...