Paste an AWS IAM policy and get flagged for the patterns that actually cause incidents: wildcard actions, iam:PassRole privilege escalation, and public trust policies. Everything runs in your browser - the policy is never sent anywhere.
These are the patterns AWS's own IAM Access Analyzer and most real security incidents keep coming back to: a bare Action: "*" or service-level wildcard (s3:*) that grants far more than a role needs, iam:PassRole combined with a wildcard resource (a well-documented privilege-escalation primitive when paired with permission to create compute resources), sts:AssumeRole with no resource scoping, and a wildcard Principal on a trust policy with no Condition - which makes a role assumable by anyone, not just your account.
This is a linter, not a full policy simulator - it flags shape, not runtime behavior. For anything touching production, cross-check with AWS IAM Access Analyzer, which evaluates against your account's actual resource policies.
Related terms: IAM • RBAC • Least Privilege
Want to actually practice cloud security and access control, not just lint one policy?
Practice Free on Zamlom