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
Hi, I searched for an flag where I can set a region for scanning. I found in the offical docs https://mondoo.com/docs/cnspec/cli/cnspec_scan_aws/ --region string AWS region to scan.
but cnspect scan aws --help says --region string Region to use for authentication with the API. Note: this does not limit the discovery to the region
So what's the truth? :)
I believe the second one. So back to the question, is there any way to set the explicit region for scanning? I tried it with default region in aws config and also with the env key "AWS_DEFAULT REGION" but no change in my results
OS: linux/macOS
OS Version: archlinux
cnspec 9.14.0
Thank you
The text was updated successfully, but these errors were encountered:
@arudat Thank you for the report. I think it would be great to add this to cnspec. Until then you can use export AWS_REGION=us-east-1 to set the region.
I have to correct myself. The AWS_REGION is only relevant for the credentials. By default, cnquery & cnspec use all regions. We have the option to set the cnquery shell aws --filters but that does not work as intended for all cases right now.
I am going to turn this into a bug since the region filter does not work right now. Until then you can use:
Hi, I searched for an flag where I can set a region for scanning. I found in the offical docs
https://mondoo.com/docs/cnspec/cli/cnspec_scan_aws/
--region string AWS region to scan.
but cnspect scan aws --help says
--region string Region to use for authentication with the API. Note: this does not limit the discovery to the region
So what's the truth? :)
I believe the second one. So back to the question, is there any way to set the explicit region for scanning? I tried it with default region in aws config and also with the env key "AWS_DEFAULT REGION" but no change in my results
Thank you
The text was updated successfully, but these errors were encountered: