IAM external access analyzer should be enabled in every region
This check looks at whether AWS IAM Access Analyzer is set up in each region you use. The safe setting is to have an external access analyzer running in all of them so that resources shared outside your account show up as findings.
Why it matters
Resources such as S3 buckets, IAM roles, KMS keys and queues can be shared with other accounts or with the public by a single policy line. Access Analyzer reads those policies and reports which resources can be reached from outside your account or organization. Without it, an accidental public grant can stay unnoticed until someone outside finds it first.
An analyzer works per region, so a region with no analyzer is a blind spot for the resources that live there. Teams often enable it in their main region and forget the others, including regions they never meant to use but where a script or a stray service created resources. The AWS documentation describes what the analyzer covers and how to create one.
How to check it yourself
Portal: AWS console → IAM → Access Analyzer → Analyzer settings. Switch the region selector through each region you use and confirm that an external access analyzer is listed and active.
Read-only command (AWS CLI, describe and list only):
for r in $(aws ec2 describe-regions --query "Regions[].RegionName" --output text); do
echo "$r"; aws accessanalyzer list-analyzers --region "$r" --query "analyzers[].{Name:name,Type:type,Status:status}" --output table
doneEvery region should show at least one analyzer with status ACTIVE. Choose the account or organization type depending on how your accounts are set up.
How to fix it
Portal: in Access Analyzer choose Create analyzer, pick the external access type, set the zone of trust to your account or your organization, name it, and create it. Repeat in each region.
Script (this creates a resource in your account, so review it before running):
for r in $(aws ec2 describe-regions --query "Regions[].RegionName" --output text); do
aws accessanalyzer create-analyzer --analyzer-name external-access --type ACCOUNT --region "$r"
doneIf a region already has an analyzer, the command reports a conflict and you can skip it. ConfigCobra reads your account and never creates the analyzer for you.
What changes when you fix it
Turning on an analyzer does not change who can access anything. It only adds findings, which will list existing sharing that you may not have known about.
Security and cloud teams should plan time to review the first findings and decide which are intended, such as a public website bucket, and which should be closed. Expect the first review to be the longest; after that the findings list is mostly new changes.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Amazon Web Services Foundations v7.0.0 | 2.18 | Level 1 |
Check this on your AWS
ConfigCobra runs this check with every other control of the CIS Amazon Web Services Benchmarks, read-only.