-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws ecr describe-image-scan-findings with no recommendations #8677
Comments
Hi @oallauddin thanks for reaching out. The AWS CLI describe-image-scan-findings involves a call to the underlying DescribeImageScanFindings API. Therefore this issue relates to the API results rather than the CLI directly. In the Response Syntax for the API it shows results for Or if there is an inconsistency between the console and API results, can you also confirm that you're using the same account for both? |
Hi @tim-finnigan , Our ECR registry is using enhanced scanning. |
Thanks for confirming. I think we will need to reach out to the ECR team regarding this issue, as they own the underlying APIs. Before forwarding this to them, could you just provide your debug logs (with sensitive info redacted) by adding |
I reached out to AWS admins and they have started AWS support issue. |
I am going to close this issue since it not AWS CLI related and is an issue with the API. The Inspector API version of the VulnerablePackage object seems to be the only way to get remediation information for a vulnerability at the moment. Remediation object in both Inspector API and ECR API appears to always have recommendation value of "None Provided". |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
aws ecr describe-image-scan-findings
is not returning the recommendations that are in AWS Inspector.Expected Behavior
Recommendations would match what is in AWS Inspector.
Current Behavior
Recommendations always come back as None Provided for all findings.
Reproduction Steps
ECR repository in us-gov-west-1 with enhanced scanning and continuous scanning enabled.
Possible Solution
No response
Additional Information/Context
No response
CLI version used
aws-cli/2.14.5 Python/3.9.16 Linux/5.15.146.1-microsoft-standard-WSL2 source/x86_64.amzn.2023 prompt/off
Environment details (OS name and version, etc.)
Amazon Linux 2023 WSL2
The text was updated successfully, but these errors were encountered: