Lifecycle and Other Bucket Configurations
In addition to lifecycle configurations, you can associate other configurations with your bucket. This section explains how lifecycle configuration relates to other bucket configurations.
Lifecycle and Versioning
You can add lifecycle configurations to unversioned buckets and versioning-enabled buckets. For more information, see Object Versioning.
A versioning-enabled bucket maintains one current object version, and zero or more noncurrent object versions. You can define separate lifecycle rules for current and noncurrent object versions.
For more information, see Lifecycle Configuration Elements. For information about versioning, see Object Versioning.
Lifecycle Configuration on MFA-enabled Buckets
Lifecycle configuration on MFA-enabled buckets is not supported.
Lifecycle and Logging
If you have logging enabled on your bucket, Amazon S3 reports the results of an expiration action as follows:
-
If the lifecycle expiration action results in Amazon S3 permanently removing the object, Amazon S3 reports it as an
S3.EXPIRE.OBJECToperation in the log record. -
For a versioning-enabled bucket, if the lifecycle expiration action results in a logical deletion of the current version, in which Amazon S3 adds a delete marker, Amazon S3 reports the logical deletion as an
S3.CREATE.DELETEMARKERoperation in the log record. For more information, see Object Versioning. -
When Amazon S3 transitions an object to the GLACIER storage class, it reports it as an operation
S3.TRANSITION.OBJECTin the log record to indicate it has initiated the operation. When the object is transitioned to the STANDARD_IA (or ONEZONE_IA) storage class, it is reported as anS3.TRANSITION_SIA.OBJECT(orS3.TRANSITION_ZIA.OBJECT) operation.
More Info
