You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction 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
If you currently scanning an Distroless-Image with Basic-Scan in ECR, you just getting no results via Console/API once Scan finished (Note: 'Fixing it' on AWS-side by returning an UnsupportedImageError would not help!). Hence, we like to get support for Distroless-Images in AWS ECR Basic Scanner!
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?
AWS ECR Basic Scanning does not support Distroless-Images for detection of vulnerabilities. AWS ECR Basic Scanning using Clair. Futhermore, AWS Basic Scanner doesn't use the current upstream release (from claircore). Clair added support via quay/claircore#181 (in 2020) and quay/claircore#1018 (in 2023) - Maybe this helps to enable/re-implement Scanning in "ECR-Clair-codebase". Sure, there are still ongoing discussions via quay/claircore#969.
Are you currently working around this issue?
We using an Ubuntu images, which are per se more vulnerable! We like to switch to Distroless, as recommended by Envoy team (envoyproxy/envoy#31015 (comment))
Additional context Here is a real life background: We are heavily relay on Envoy Proxy within our AWS ECR cluster setup (yes, we doesn't use the new, fancy AWS App Mesh - we are using patterns like: https://aws.amazon.com/de/blogs/compute/setting-up-an-envoy-front-proxy-on-amazon-ecs/). Envoy recently stopped built & provide Alpine Images. Having this said, now only Ubuntu-based and Distroless-based Images for Envoy Proxy are available. As a first step, we tried the Ubuntu-based Image: We saw a bunch of security issues, which we highlighted here: envoyproxy/envoy#31015 As a next steps, we moved to the Distroless-based Images of Envoy Proxy. Since we integrated ECR Basic Scanning within our Pipelines (proceed with deployment based on the return of Basic-Scan), a switch to Enhanced Scanning is not an (easy) option yet for us.
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
If you currently scanning an Distroless-Image with Basic-Scan in ECR, you just getting no results via Console/API once Scan finished (Note: 'Fixing it' on AWS-side by returning an UnsupportedImageError would not help!). Hence, we like to get support for Distroless-Images in AWS ECR Basic Scanner!
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?
AWS ECR Basic Scanning does not support Distroless-Images for detection of vulnerabilities. AWS ECR Basic Scanning using Clair. Futhermore, AWS Basic Scanner doesn't use the current upstream release (from claircore). Clair added support via quay/claircore#181 (in 2020) and quay/claircore#1018 (in 2023) - Maybe this helps to enable/re-implement Scanning in "ECR-Clair-codebase". Sure, there are still ongoing discussions via quay/claircore#969.
Are you currently working around this issue?
We using an Ubuntu images, which are per se more vulnerable! We like to switch to Distroless, as recommended by Envoy team (envoyproxy/envoy#31015 (comment))
Additional context
Here is a real life background: We are heavily relay on Envoy Proxy within our AWS ECR cluster setup (yes, we doesn't use the new, fancy AWS App Mesh - we are using patterns like: https://aws.amazon.com/de/blogs/compute/setting-up-an-envoy-front-proxy-on-amazon-ecs/). Envoy recently stopped built & provide Alpine Images. Having this said, now only Ubuntu-based and Distroless-based Images for Envoy Proxy are available. As a first step, we tried the Ubuntu-based Image: We saw a bunch of security issues, which we highlighted here: envoyproxy/envoy#31015 As a next steps, we moved to the Distroless-based Images of Envoy Proxy. Since we integrated ECR Basic Scanning within our Pipelines (proceed with deployment based on the return of Basic-Scan), a switch to Enhanced Scanning is not an (easy) option yet for us.
The text was updated successfully, but these errors were encountered: