AWS AmazonS3 documentation change
Summary
Added clarification that objects with FAILED replication status will not have a lifecycle expiration date populated in inventory reports, as S3 Lifecycle prevents expiration/transition actions until replication succeeds.
Security assessment
This change documents existing S3 Lifecycle behavior regarding replication status and expiration dates. It clarifies functionality but does not address any security vulnerability or weakness. The change is informational about how lifecycle rules interact with replication status.
Diff
diff --git a/AmazonS3/latest/userguide/storage-inventory.md b/AmazonS3/latest/userguide/storage-inventory.md index 8078cd0d4..a78e824b6 100644 --- a//AmazonS3/latest/userguide/storage-inventory.md +++ b//AmazonS3/latest/userguide/storage-inventory.md @@ -166 +166 @@ To get the decoded value in JSON for the Object ACL field, you can query this fi - * **Lifecycle Expiration Date** – Set to the lifecycle expiration timestamp of the object. This field will only be populated, if the object is to be expired by an applicable lifecycle rule. In other cases, the field will be empty. For more information, see [Expiring objects](./lifecycle-expire-general-considerations.html). + * **Lifecycle Expiration Date** – Set to the lifecycle expiration timestamp of the object. This field will only be populated, if the object is to be expired by an applicable lifecycle rule. In other cases, the field will be empty. Objects with `FAILED` replication status will not have an expiration date populated, as S3 Lifecycle prevents expiration and transition actions on these objects until replication has succeeded. For more information, see [Expiring objects](./lifecycle-expire-general-considerations.html).