Lifecycle and other bucket configurations - Amazon Simple Storage Service
Lifecycle and versioning Lifecycle configuration on MFA-enabled bucketsLifecycle and loggingTroubleshooting S3 LifecycleMore info
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Lifecycle and other bucket configurations

In addition to S3 Lifecycle configurations, you can associate other configurations with your bucket. This section explains how S3 Lifecycle configuration relates to other bucket configurations.

Lifecycle and versioning

You can add S3 Lifecycle configurations to unversioned buckets and versioning-enabled buckets. For more information, see Using versioning in S3 buckets.

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.

Important

When you have multiple rules in an S3 Lifecycle configuration, an object can become eligible for multiple S3 Lifecycle actions on the same day. In such cases, Amazon S3 follows these general rules:

  • Permanent deletion takes precedence over transition.

  • Transition takes precedence over creation of delete markers.

  • When an object is eligible for both a S3 Glacier Flexible Retrieval and S3 Standard-IA (or S3 One Zone-IA) transition, Amazon S3 chooses the S3 Glacier Flexible Retrieval transition.

For examples, see Example 5: Overlapping filters, conflicting lifecycle actions, and what Amazon S3 does with nonversioned buckets.

Lifecycle configuration on MFA-enabled buckets

Lifecycle configuration on multi-factor authentication (MFA)-enabled buckets is not supported.

Lifecycle and logging

Amazon S3 Lifecycle actions are not captured by Amazon CloudTrail object level logging. CloudTrail captures API requests made to external Amazon S3 endpoints, whereas S3 Lifecycle actions are performed using internal Amazon S3 endpoints. Amazon S3 server access logs can be enabled in an S3 bucket to capture S3 Lifecycle-related actions such as object transition to another storage class and object expiration resulting in permanent deletion or logical deletion. For more information, see Logging requests with server access logging.

If you have logging enabled on your bucket, Amazon S3 server access logs report the results of the following operations.

Operation log Description

S3.EXPIRE.OBJECT

Amazon S3 permanently deletes the object because of the Lifecycle expiration action.

S3.CREATE.DELETEMARKER

Amazon S3 logically deletes the current version and adds a delete marker in a versioning-enabled bucket.

S3.TRANSITION_SIA.OBJECT

Amazon S3 transitions the object to the S3 Standard-IA storage class.

S3.TRANSITION_ZIA.OBJECT

Amazon S3 transitions the object to the S3 One Zone-IA storage class.

S3.TRANSITION_INT.OBJECT

Amazon S3 transitions the object to the S3 Intelligent-Tiering storage class.

S3.TRANSITION_GIR.OBJECT

Amazon S3 initiates the transition of the object to the S3 Glacier Instant Retrieval storage class.

S3.TRANSITION.OBJECT

Amazon S3 initiates the transition of the object to the S3 Glacier Flexible Retrieval storage class.

S3.TRANSITION_GDA.OBJECT

Amazon S3 initiates the transition of the object to the S3 Glacier Deep Archive storage class.

S3.DELETE.UPLOAD

Amazon S3 aborts an incomplete multipart upload.
Note

Amazon S3 server access log records are generally delivered on a best-effort basis and cannot be used for complete accounting of all Amazon S3 requests.

Troubleshooting S3 Lifecycle

For more information about troubleshooting common issues with S3 Lifecycle, see Troubleshoot Amazon S3 Lifecycle issues.

More info