Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[ECR] [Cross region replication of existing images]: Feature that allows automatic replication of existing images without update #1289

Open
JoeDurrant opened this issue Feb 25, 2021 · 8 comments
Labels
ECR Amazon Elastic Container Registry Proposed Community submitted issue

Comments

@JoeDurrant
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
What do you want us to build?
Currently the ECR cross region replication (CRR) feature only replicates images and repositories when an update is made after enabling CRR. This means that images that do not get updated will never be replicated, even if this is wanted. I'm requesting a feature that will give the option of replicating all repositories and images in the specified registry, or some kind of filter which allows a desired list of existing repositories/images to be replicated without having to update them.

Which service(s) is this request for?
ECR

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I'm trying to replicate an ECR registry into another region for availability/disaster recovery purposes, but the images which have not/will not be updated since cross region replication will not replicate until an update. We have a huge amount of repos and images within them, and it will be a tedious and very manual process to update each of them in a way that will force the replication to take place. Would be much easier to have an additional option that allows this to be done automatically.

Are you currently working around this issue?
Manually updating images to force through the replication.

Additional context
Anything else we should know?

Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

@JoeDurrant JoeDurrant added the Proposed Community submitted issue label Feb 25, 2021
@RLThomaz
Copy link

RLThomaz commented Mar 2, 2021

I believe this is a duplicate of #1252. Meanwhile, I'd suggest writing a script that takes all image manifests, delete the images, and immediately push them back. I've achieved that using the AWS Node.js SDK.

@pdhav
Copy link

pdhav commented Nov 17, 2021

+1 as it closely matches my part of my request to AWS support team.

@gregory-v
Copy link

+1

1 similar comment
@himalayKondekar
Copy link

+1

@sethatron
Copy link

+1

@wosiu
Copy link

wosiu commented Nov 20, 2023

There is also a proposal for ECR to ECR pull-through cache, which could replace full replication that is discussed in this ticket. I think it would also address the issue described in this ticket - already existing images in region A would be cached in region B on demand automatically.
Also that way you would not replicate images that are maybe no longer needed in a target region (saving $$$ on transfer and storage in the new region).
If you think it would help - vote: #2208

@yardenws
Copy link

+1

1 similar comment
@pa-ssek
Copy link

pa-ssek commented Jan 22, 2025

+1

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
ECR Amazon Elastic Container Registry Proposed Community submitted issue
Projects
None yet
Development

No branches or pull requests

10 participants