PuppyIP Resource Center
Cloud Operations 4 min Published 2026-11-18

Does Amazon ECR Replicate Image Deletions? Setup and Rollback Retention

Amazon ECR leaves destination images in place when you delete a source image by default. Enable deleteReplication on a private image replication rule to propagate future image deletions and tag removals. If you keep rollback images in a destination registry, check whether that destination is covered by the rule.

Amazon ECR Image replication Lifecycle policies Rollback

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • AWS announced cross-Region and cross-account delete replication for private image replication rules on November 16, 2026.
  • Image expiration under a source lifecycle policy also triggers delete replication. Deleting a source repository leaves destination repositories in place.
  • For cross-account replication, the destination registry policy must also grant ecr:ReplicateImageDelete to the source account.

Which actions affect the destination repository?

When an image has several tags, removing one tag removes only that tag at the destination. Removing the last tag or deleting by digest deletes the matching image digest and its tags at the destination. A digest identifies the contents of a particular image.

A source lifecycle policy that expires an image also triggers a replicated deletion. Set your rollback retention with both the source cleanup policy and the replication destinations in mind.

How do you check a rule's scope?

In the source account's private registry replication configuration, review the matching repositories, destination accounts, and AWS Regions. To opt in for a single rule, set the enabled field in that rule's deleteReplication object to true. The setting applies to deletions made after it is enabled.

For a different destination account, check its registry permissions policy as well. Alongside existing image replication permissions, it must grant ecr:ReplicateImageDelete to the source account. Repository-level permissions or a change to the source rule alone cannot supply that registry permission.

Why is the image still visible at the destination?

Replication is asynchronous. Pushes and deletions can arrive at the destination in a different order from the source. ECR applies the deletion only while the destination content still matches. If the image or tag is already gone or a newer action changed it, the replicated deletion has no further effect.

In the destination Region, look for a completed ECR Replication Action event in EventBridge with action-type REPLICATE_DELETE. For cross-account replication, you can also check the destination account's CloudTrail logs for ReplicateImageDelete. Match the repository, Region, account, and image digest when reviewing the records.

How can you tell tag removal from image deletion?

Release pipelines often give the same image a version tag and a latest tag. Check whether the source action removed one tag, the last tag, or the entire digest. Then inspect both the digest and the tags at the destination. If latest still exists, check whether it now points to a newer image.

Handle repository deletion separately from image cleanup. When someone deletes the source repository, review the destination's remaining images and retention policies separately.

What should you check to keep rollback images?

Suppose your release repository keeps images for 7 days and your backup repository needs them for 30. If the backup is a destination covered by delete replication, expiration in the release repository on day 7 can affect the backup copy. Keep any images that need independent retention somewhere outside the rule's deletion scope and verify that your rollback job can pull them by digest.

AWS says delete replication is available in every AWS Region that offers ECR and carries no additional charge. The user guide gives no fixed propagation time. Check actual replication events in the destination Region when planning cleanup windows.

Sources

Frequently Asked Questions

If images replicate from A to B and then B to C, will deletion reach C?

If the rule in A lists only B as a destination, the replicated deletion from A reaches B. B does not forward the same deletion to C.

Will enabling it clean up images deleted before I enabled the rule?

No. Replication covers only deletions and tag removals after opt-in. Compare the source and destination repositories separately when checking older differences.