AWS Security ChangesHomeSearch

AWS AmazonS3: Clarify S3 Tables snapshot expiration and unreferenced file removal behavior

Service: AmazonS3 · 2026-09-30 · Documentation low

File: AmazonS3/latest/userguide/s3-tables-considerations.md

Summary

Adds considerations explaining that snapshot expiration ignores unreferencedDays and object creation time, and warns that delayed commits can cause objects to be marked noncurrent and permanently deleted, causing query failures and unrecoverable data loss.

Security assessment

This is a data-durability/operational guidance change about lifecycle timing, not a vulnerability, credential, or access-control fix. It warns of potential data loss but does not address a security weakness.

Evidence

+  * **Delayed commits** – Workloads such as high-throughput streaming pipelines can create data objects before a commit adds references to those objects in a table snapshot. Configure `unreferencedDays` to be longer than the maximum expected time between object creation and successful commit completion, including processing delays and retries.

Diff

diff --git a/AmazonS3/latest/userguide/s3-tables-considerations.md b/AmazonS3/latest/userguide/s3-tables-considerations.md
index fe447f5..992ac9b 100644
--- a//AmazonS3/latest/userguide/s3-tables-considerations.md
+++ b//AmazonS3/latest/userguide/s3-tables-considerations.md
@@ -56,0 +57,2 @@ The following considerations apply to snapshot management. For more information
+  * Snapshot expiration does not use `unreferencedDays` (a setting for unreferenced file removal) or evaluate an object's creation time. When snapshot expiration removes the last snapshot reference to an object, Amazon S3 immediately marks the object as noncurrent, regardless of its age. Amazon S3 permanently deletes the object after the configured `nonCurrentDays` period.
+
@@ -65,0 +68,4 @@ The following considerations apply to unreferenced file removal. For more inform
+  * **Delayed commits** – Workloads such as high-throughput streaming pipelines can create data objects before a commit adds references to those objects in a table snapshot. Configure `unreferencedDays` to be longer than the maximum expected time between object creation and successful commit completion, including processing delays and retries.
+
+If an object reaches the configured `unreferencedDays` age before its commit completes, Amazon S3 marks the object as noncurrent because no snapshot references it yet. If a later commit then references that object, queries and maintenance operations that read it fail. Amazon S3 permanently deletes the noncurrent object after the configured `nonCurrentDays` period, and the object cannot be recovered.
+