[ECS] [request]: Publish region-specific ECR public repos for ecs-agent image
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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**
Opening this on behalf of a customer (https://github.com/aws/amazon-ecs-agent/issues/2526).
Launching ecs-agent out of Dockerhub relies on Dockerhub availability, for which most ECS users will not have a support relationship. Publish the ECS agent in all of the region-specific ECR repositories in the same way as https://github.com/aws/aws-for-fluent-bit.
**Which service(s) is this request for?**
ECS, ECR
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
AWS has the infrastructure to host the ECS Agent image on per-region ECR repositories. This should be done to remove the requirement that Dockerhub be available to launch new nodes. This is particularly important in an autoscaling scenario. AWS customers have a commercial relationship with AWS so can reasonably expect support for the availability of ECR, not so much with Dockerhub.
https://github.com/aws/aws-for-fluent-bit already does something similar.
**Are you currently working around this issue?**
Relying on Dockerhub
Contributor guide
Research direction
Start by reviewing the request and comparing it with the linked aws-for-fluent-bit approach for region-specific ECR repositories. Done would mean the ECS agent image is published in all region-specific ECR repositories so launching new nodes no longer depends on Dockerhub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100