Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

ECR assets: potential service limit issues #5970

Closed
eladb opened this issue Jan 27, 2020 · 3 comments
Closed

ECR assets: potential service limit issues #5970

eladb opened this issue Jan 27, 2020 · 3 comments
Assignees
Labels
bug This issue is a bug.

Comments

@eladb
Copy link
Contributor

eladb commented Jan 27, 2020

Originally posted by @caruso-billfire in #5733 (comment)

If I am understanding this correctly if you have N number of Dockerfiles they will all be pushed to the same ECR Repo now?

I feel like service limits were not thought about in this decision. For Organizations wanting to use the CDK who also have a ton of Docker Images they need to store; this cdk construct will lead to service limit related issues.

https://docs.amazonaws.cn/en_us/AmazonECR/latest/userguide/service-quotas.html

@eladb eladb self-assigned this Jan 27, 2020
@eladb eladb added bug This issue is a bug. p1 labels Jan 27, 2020
@eladb
Copy link
Contributor Author

eladb commented Jan 27, 2020

@caruso-billfire do you anticipate a single account/region with over 10,000 images actively being used (consider that the CDK will garbage collect unused images)

@eladb
Copy link
Contributor Author

eladb commented Feb 3, 2020

We verified with the ECR team that there shouldn't be any issues related performance

@eladb
Copy link
Contributor Author

eladb commented Feb 3, 2020

Closing this for now. Please reopen if you there is additional information/feedback that you wish to provide on this topic.

@eladb eladb closed this as completed Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

No branches or pull requests

1 participant