AWS AmazonECR documentation change
Summary
Clarified replication behavior for restored images and archive status handling
Security assessment
Changes explain replication mechanics for restored/archived images but don't address security vulnerabilities or introduce security features.
Diff
diff --git a/AmazonECR/latest/userguide/replication.md b/AmazonECR/latest/userguide/replication.md index 39654f0a6..af69963e9 100644 --- a//AmazonECR/latest/userguide/replication.md +++ b//AmazonECR/latest/userguide/replication.md @@ -137 +137 @@ The following should be considered when using private image replication. - * Only repository content pushed to a repository after replication is configured is replicated. Any preexisting content in a repository isn't replicated. Once replication is configured for a repository, Amazon ECR keeps the destination and source synchronized. + * Only repository content pushed or restored to a repository after replication is configured is replicated. Any preexisting content in a repository isn't replicated. If an image is restored after replication is turned on, it will be replicated. If it is restored before replication is turned on, it won't be replicated. @@ -155 +155 @@ The following should be considered when using private image replication. - * A replication action only occurs once per image push. For example, if you configured cross-Region replication from `us-west-2` to `us-east-1` and from `us-east-1` to `us-east-2`, an image pushed to `us-west-2` replicates to only `us-east-1`, it doesn't replicate again to `us-east-2`. This behavior applies to both cross-Region and cross-account replication. + * A replication action only occurs once per image push or image restore. For example, if you configured cross-Region replication from `us-west-2` to ` us-east-1` and from `us-east-1` to `us-east-2`, an image pushed to `us-west-2` replicates to only `us-east-1`, it doesn't replicate again to `us-east-2`. This behavior applies to both cross-Region and cross-account replication. @@ -159 +159,5 @@ The following should be considered when using private image replication. - * Registry replication doesn't perform any delete actions. Replicated images and repositories can be manually deleted when they are no longer being used. + * Registry replication doesn't perform any delete actions or archive actions. Replicated images and repositories can be deleted or archived when they are no longer being used. + + * If the image to be replicated is archived in the destination, then it will be restored in the destination. + + * When an image is archived in a source region, it will not be archived in a destination region specified by the replication configuration.