AWS AmazonS3 documentation change

Service: AmazonS3 · 2026-06-19 · Documentation low

File: AmazonS3/latest/userguide/replication-what-is-isnot-replicated.md

Summary

Added details about annotation replication behavior during live and batch replication, including non-replication of deletions and accumulation risks.

Security assessment

The change documents operational behavior of annotation replication (non-replication of deletions leading to accumulation) but doesn't address security vulnerabilities or introduce security features. It focuses on functional characteristics rather than security controls.

Diff

diff --git a/AmazonS3/latest/userguide/replication-what-is-isnot-replicated.md b/AmazonS3/latest/userguide/replication-what-is-isnot-replicated.md
index da794ab7f..e7644cb08 100644
--- a//AmazonS3/latest/userguide/replication-what-is-isnot-replicated.md
+++ b//AmazonS3/latest/userguide/replication-what-is-isnot-replicated.md
@@ -45,0 +46,2 @@ It can take a while until Amazon S3 can bring the two ACLs in sync. This change
+  * Object annotations, if there are any. Each annotation replicates independently as changes occur during live replication. During S3 Batch Replication, annotations are replicated independently alongside the object, but there are no separate job tasks for individual annotations. If annotation replication fails, the job task fails, but the object's replication status does not reflect the annotation failure.
+
@@ -107,0 +110,6 @@ To replicate objects that have been tagged after the `PutObject` operation, you
+  * Annotation deletions on the source bucket are not replicated to the destination. If you delete an annotation on the source, the annotation persists on the replica. You cannot exclude annotations from replication using replication rule filters. When replication is configured, all annotation creates and updates are replicated unless the replication role policy explicitly denies `s3:ReplicateObjectAnnotation`.
+
+If annotations are repeatedly deleted and recreated on the source with different names, the destination replica accumulates annotations over time because deletions are not replicated. This accumulation can eventually cause the destination to exceed the 1,000 annotation limit per object version.
+
+Annotation overwrites (updates to an existing annotation name) at the source are replicated to the destination. The destination annotation content stays current with the source.
+