aws / aws/containers-roadmap

[ecr-public] [feature request]: publish vulnerability scanning results

Open
#2,025 0 comments 8 reactions 0 assignees View on GitHub
ECR ECR Public 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**
Please expose vulnerability scanning results also for the public ECR. The results shall be visible as the best security practice.

**Which service(s) is this request for?**
ECR public repository

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
As an AWS customer, I'd like to benefit from the fact I am already on platform and recommend AWS ECR public registry as a secure, fast and generally good source of base images for our services.
As an external user, I admire AWS and I believe they offer always the most secure, trustable and enterprise grade services. This why I want to use ECR public registries as a good source for my base images.
Unfortunately, there is no possibility to find the least vulnerable image just from checking out the scanning results and it requires user to re-push an image into their own private ECR in order to see the vulnerability scanning results.

**Are you currently working around this issue?**
Using different public Docker registries.

**Additional context**
You can take RedHat operated public Docker registry as a very good example of how such service should look like. [Here is their container vulnerability view example](https://catalog.redhat.com/software/containers/openshift3/ose-pod/57ea8d029c624c035f96f424?container-tabs=security), all important information at one place.

**Attachments**
-

Contributor guide

Open the contributing guide

Research direction

The issue names no repository files, tests, or entry points. Start by reviewing the public ECR service and the linked Red Hat vulnerability view to define the required result presentation; done means vulnerability scanning results are available for public ECR images without re-pushing them to a private repository.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.