aws / aws/containers-roadmap

[ECR] [request]: Registry configuration to reject requests without a digest

Open
#2,539 0 comments 0 reactions 0 assignees View on GitHub
ECR Proposed
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**
Introduce a configuration on for each ECR registry to reject requests without a digest.

**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?**
Whilst immutable tags are great, to encourage everyone to use digests image in helm charts / etc.
I would like the option to enforce that at repository level.

**Are you currently working around this issue?**
No

**Additional context**
Best practices is to use digest for images, to ensure that they can't be swapped.

**Attachments**

Contributor guide

Open the contributing guide

Research direction

No source files, tests, or entry points are identified in the issue. Start by reviewing how AWS ECR registry and repository configuration is represented, then define the configuration scope and request behavior; done means a repository-level option can reject image requests that do not use a digest.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.