AWS AmazonS3 documentation change
Summary
Added documentation about S3 Lifecycle interaction with S3 Replication, clarifying that expiration/transition actions are blocked for objects with PENDING/FAILED replication status.
Security assessment
Change explains feature behavior to prevent premature object expiration during replication, which improves data durability but does not address security vulnerabilities or document security features. No evidence of security vulnerability remediation.
Diff
diff --git a/AmazonS3/latest/userguide/lifecycle-and-other-bucket-config.md b/AmazonS3/latest/userguide/lifecycle-and-other-bucket-config.md index 18efea532..b03fd3244 100644 --- a//AmazonS3/latest/userguide/lifecycle-and-other-bucket-config.md +++ b//AmazonS3/latest/userguide/lifecycle-and-other-bucket-config.md @@ -7 +7 @@ -S3 Lifecycle and S3 VersioningS3 Lifecycle andS3 Lifecycle configuration on MFA-enabled bucketsS3 Lifecycle and logging +S3 Lifecycle and S3 VersioningS3 Lifecycle and S3 ReplicationS3 Lifecycle configuration on MFA-enabled bucketsS3 Lifecycle and logging @@ -36 +36 @@ For examples, see [Examples of overlapping filters and conflicting lifecycle act -## S3 Lifecycle and +## S3 Lifecycle and S3 Replication @@ -38 +38 @@ For examples, see [Examples of overlapping filters and conflicting lifecycle act -When you have both and S3 Lifecycle enabled on a bucket, S3 Lifecycle blocks expiration and transition actions on objects with `PENDING` or `FAILED` replication status. This ensures that Lifecycle does not act on objects until they have successfully replicated to their destination bucket. +When you have both S3 Replication and S3 Lifecycle enabled on a bucket, S3 Lifecycle blocks expiration and transition actions on objects with `PENDING` or `FAILED` replication status. This ensures that Lifecycle does not act on objects until they have successfully replicated to their destination bucket.