[ECR] [request]: Support Docker Hardened Images (DHI) for pull through cache
- 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**
We request that AWS ECR pull-through cache support Docker Hardened Images from the `dhi.io` registry.
Example image reference: `dhi.io/python:3.10-alpine3.22`
**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?**
We want to use ECR pull-through cache for the `dhi.io` registry to leverage Docker Hardened Images in our AWS container workloads. Currently, ECR pull-through cache supports Docker Hub and other registries, but does not support `dhi.io`.
Contributor guide
Research direction
Start with the issue requirements for AWS ECR pull-through cache and the example reference dhi.io/python:3.10-alpine3.22. Review how ECR currently supports upstream registries; done means pull-through caching works for dhi.io images without changing the requested image reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100