Skip to content
IAM Policy Generator

IAM Access Analyzer finds external, internal and unused access and checks policies

AWS says IAM Access Analyzer identifies resources shared with external entities, reports internal access to chosen resources, finds unused access, validates policies, runs custom policy checks and generates policies from CloudTrail activity. This page summarizes each capability from AWS documentation read on 16 Nov 2026.

Open the workbench ยท All guides

Three analyzer types produce findings

External access analyzers use logic-based reasoning to analyze the resource-based policies in your environment. For each resource shared outside the zone of trust, which is the organization or account you chose when you created the analyzer, the analyzer generates a finding with the resource, the external principal and the permissions granted. AWS says new or changed policies are analyzed within about 30 minutes, and that a delivery problem can leave a change to the next periodic scan, within 24 hours.

Internal access analyzers, added on 16 June 2025 according to the IAM document history, show which principals in your organization or account can reach the resources you select. AWS lists six resource types for internal access: S3 buckets, S3 directory buckets, RDS DB snapshots, RDS DB cluster snapshots, DynamoDB streams and DynamoDB tables.

Unused access analyzers monitor roles and users and report unused roles, unused access keys, unused passwords and, for active identities, unused services and actions. They rely on last accessed information.

AnalyzerQuestion it answersRegional behavior per AWS
External accessWhich resources are shared outside the zone of trustAnalyzes policies in the Region where it is enabled; create one per Region
Internal accessWhich principals inside the organization reach selected resourcesEnabled per Region
Unused accessWhich roles, keys, passwords, services and actions are unusedFindings do not change by Region; one analyzer is enough

Policy validation runs before you save a policy

Policy validation checks a policy against IAM policy grammar and AWS best practices. Findings come in four kinds: security warnings, errors, general warnings and suggestions. AWS says the console shows them when you create or edit a managed policy and for inline user or role policies, but not for inline group policies. The best practices page says validation provides more than 100 checks, and the check reference page lists them by name.

The AWS CLI command is aws accessanalyzer validate-policy, which takes a policy document and a policy type and returns a list of findings.

Custom policy checks compare a policy to a standard you set

Custom policy checks test a policy against your own security standard. Through the console you can check whether an updated policy grants new access compared with the existing version. Through the CLI or API three checks are available: check-no-new-access, which compares an updated policy with an existing one; check-access-not-granted, which confirms specified actions are not allowed; and check-no-public-access, which checks whether a resource policy can grant public access to a resource type.

AWS states that a charge applies to each check for new access. Its pricing page, read 16 Nov 2026, lists custom policy checks as a paid feature charged by the number of checks run through the API, and lists policy validation and external access analyzers as provided at no additional charge. Internal access and unused access analyzers are paid features, billed per resource monitored and per IAM role or user, respectively.

Policy generation turns CloudTrail activity into a policy template

Access Analyzer reads CloudTrail events for a user or role over a period of up to 90 days and creates a policy that contains the actions and services the entity used. You review and customize the template, then save it as a managed policy and attach it. AWS lists limits: a CloudTrail trail must be enabled, action-level activity for data events such as S3 data events is not identified, and iam:PassRole needs attention after generation. The CLI command is aws accessanalyzer start-policy-generation.

The generated policy is a starting point from observed use. It shows what an entity did in the period, not what it will need next quarter.

The workbench covers policy text; Access Analyzer covers an account

The workbench on this site checks the text of a policy you paste, in your browser, with no account access. It does not create analyzers, read CloudTrail or produce findings about live resources. Access Analyzer works in the opposite direction: it needs an account, creates findings for resources in that account and is the AWS tool for external, internal and unused access. The two overlap only on policy checks, and the workbench's six checks are a small set next to the check reference AWS publishes. The best practices page shows where each Access Analyzer capability fits.

Sources

  1. What is IAM Access Analyzer?, read 16 Nov 2026
  2. Validate policies with IAM Access Analyzer, read 16 Nov 2026
  3. Custom policy checks, read 16 Nov 2026
  4. IAM Access Analyzer policy generation, read 16 Nov 2026
  5. Getting started with IAM Access Analyzer, read 16 Nov 2026
  6. Document history for IAM, read 16 Nov 2026
  7. validate-policy, AWS CLI command reference, read 16 Nov 2026
  8. AWS IAM Access Analyzer pricing, read 16 Nov 2026

Last reviewed 16 Nov 2026.