Skip to content
Cloud Governance Tools

IAM Access Analyzer checks a guardrail policy before you apply it and finds access it missed afterward, and leaves enforcement to SCPs, RCPs and boundaries

IAM Access Analyzer validates policies against grammar and AWS best practices, runs custom checks for new access, and keeps analyzers for external, internal and unused access. This guide separates what it does before a policy change from what it reports afterward, and what it leaves to SCPs and RCPs.

See the ranking ยท All guides

Policy validation is the first check on any guardrail JSON

Policy validation checks a policy against IAM policy grammar and AWS best practices. Findings come as security warnings, errors, general warnings and suggestions. In the IAM console they appear for managed policies and for inline user and role policies, and AWS notes they are not generated for inline group policies. Run it on every guardrail file, since a syntax error found at attach time is slower to fix.

The check reference includes checks written for SCPs. One example is the error "SCP syntax error action wildcard": SCP actions can include wildcards only at the end of a string. A guardrail JSON file copied from the library can be run through validation before it is attached, and catching a bad wildcard here is cheaper than a failed attachment. Each finding also names the location of the reported issue.

Custom policy checks answer whether an edit grants new access

Custom policy checks test a policy against your own security standard. In the console, you can edit a policy and check whether the new version grants new access compared with the existing one. Through the CLI and API, check-no-new-access does the same comparison, check-access-not-granted verifies that named actions are not allowed, and check-no-public-access tests whether a resource policy can grant public access.

AWS notes that a charge applies to each check for new access. For a team that edits guardrail policies through a pipeline, check-access-not-granted is the closest fit: it asserts that critical actions stay unreachable after every change. Put it in the same pipeline step that validates the JSON, and fail the build when a check returns a finding, so an IAM policy edit cannot widen access by accident.

External and internal access analyzers preview resource policies

An external access analyzer uses logic-based reasoning on resource-based policies and produces a finding for each resource shared outside your account or organization. AWS says the findings can be used to preview how a policy affects public and cross-account access before deploying resource permissions. External analyzers analyze only policies applied to resources in the same Region, so create one in each Region where you use resources.

That preview is the closest AWS tool for the situation an RCP addresses, access to a resource from outside. Internal access analyzers cover access from principals within your own organization to selected resources, such as S3 buckets and DynamoDB tables. Neither type changes any policy. They report. Internal access findings show access paths between principals and resources, which helps verify that your access controls work as intended.

Unused access findings show what a guardrail should cover next

An unused access analyzer continuously monitors IAM roles and users in your organization and produces findings for unused roles, unused access keys and unused passwords. For active roles and users, the findings show unused services and actions. Findings are organized in a dashboard that highlights the accounts and resources with the most findings and breaks them down by type, which gives a review meeting a ranked list to work from.

Those findings feed the next guardrail. A service no role has used in the review period is a candidate for an SCP deny, and the SCP page makes a related point: service last accessed data shows which services an SCP allows but nobody uses. Policy generation can also build an IAM policy from CloudTrail activity over a date range, which you then attach to refine one identity.

What it leaves to other mechanisms

IAM Access Analyzer reports and validates. AWS does not describe it in the request path, so it is no substitute for an SCP, an RCP or a permissions boundary. Findings arrive after access exists, which makes it a detective tool, in the sense used in preventive vs detective controls. Treat a finding as a prompt to open a change, not as a control. Blocking is left to those mechanisms.

Use it at two points: before an edit, to validate syntax and prove no new access was granted, and on a schedule afterward, to find exposure and unused permissions. The policy simulator, covered in testing a guardrail first, answers a different question: whether a specific request is allowed. Schedule the second use monthly, and attach an owner's name to each class of finding.

Cost and scope are documented and worth checking first

AWS states that a charge applies to each custom check for new access, and that unused access analysis is charged by the number of IAM roles and users analyzed, with a charge for each unused access analyzer you create. Read the IAM Access Analyzer pricing page before you add checks to a pipeline that runs on every commit. Budget both.

For unused access, AWS says findings do not change by Region, so you do not need an analyzer in each Region. External access analyzers are per Region. Plan the analyzers by account and Region before you create them, and decide who reads the findings. Decide who reads the findings. Assign a named owner for each analyzer type.

Sources

  1. IAM: Using IAM Access Analyzer, read 10 Nov 2026
  2. IAM: Validate policies with IAM Access Analyzer, read 10 Nov 2026
  3. IAM: Custom policy checks, read 10 Nov 2026
  4. IAM: Access Analyzer policy check reference, read 10 Nov 2026
  5. IAM: Generate policies based on access activity, read 10 Nov 2026
  6. AWS Organizations: Service control policies, read 10 Nov 2026

Last reviewed 16 Nov 2026.