AWS IAM Policy Linter
Paste an IAM policy and get a list of findings by severity: wildcard access, risky actions, bad Effect values, conflicting keys and a missing Version.
Use the tool
Why this tool exists
IAM policies tend to grow by copy and paste until nobody is sure what they allow. A single Action of star on Resource of star gives full administrator rights, and actions like iam:PassRole or iam:CreatePolicyVersion can let a user escalate their own permissions. These are easy to miss in a long document.
This linter reads the policy locally and flags the usual problems: missing or old Version, malformed actions, duplicate Sids, Action and NotAction together, wide wildcards, a public Principal without a Condition. It is a quick review aid with a short rule list. It does not replace IAM Access Analyzer or testing in the policy simulator.
How to use it
- Paste the policy JSON, including the Version and Statement keys.
- Read the findings, each tagged CRITICAL, HIGH, MEDIUM, LOW, WARNING or ERROR.
- Fix the policy, paste it again, and confirm with IAM Access Analyzer before deploying.
Frequently asked questions
What does it flag as critical?
An Allow with Action star on Resource star, which is full administrator access, and a public Principal star with no Condition. Both deserve an immediate rewrite.
Does it check against the real AWS action list?
No. It checks the pattern service:Action and a short list of known risky actions. It cannot tell you whether an action exists or what it really grants.
Why does it warn about the Version?
Without 2012-10-17, policy variables such as aws:username are not evaluated. Older version dates are treated the same way, so set the newer value.
Is the policy sent anywhere?
No, it is analysed in your browser. Even so, replace real account IDs and ARNs you want kept private before sharing screenshots of the results.