IAM Policy Statement Summary

Before diving into a line-by-line review of an IAM policy, it helps to see the shape of it first: how many statements it has, how many are Allow vs Deny, how many wildcard uses it contains, whether any statement grants unrestricted * on * access, and whether the document is anywhere near an IAM size limit. IAM Policy Statement Summary pastes one policy document and produces exactly that dashboard, composed entirely from the shared policy engine's existing analyzers.

Every number on the dashboard is a direct readout of an existing, separately-documented function: statement/Allow/Deny counts come from the same counting logic used elsewhere in this tool suite, wildcard findings come from the same structural wildcard scan used by the dedicated Wildcard Analyzer tool, the overly-permissive count comes from the same narrow Action:"*"+Resource:"*" check used by the dedicated Overly-Permissive Policy Checker tool, and the size numbers come from the same whitespace-stripped character count AWS itself uses for its quota, checked against all four IAM policy size limits at once (managed policy, role inline, user inline, group inline).

This tool does not introduce any new analysis — it is a single-glance composite of statistics that already exist individually elsewhere in the suite, so you can get an at-a-glance read on a policy's size and risk profile without running four separate tools first.

• Statement / Allow / Deny counts for the whole document.
• Wildcard findings count across Action/NotAction/Resource/NotResource fields.
• Overly-permissive statement count (Action "*" + Resource "*").
• Character count (whitespace-stripped) checked against all four IAM size limits with a pass/fail indicator each.
• Sample policy to see the tool in action immediately.
• 100% client-side — nothing is uploaded.

1. Paste a policy document or click the sample.
2. Click Summarize.
3. Read the stats grid — statement counts, wildcard findings, overly-permissive count, and character count.
4. Check the size-limit rows to see pass/fail against each of the four IAM inline/managed policy limits.

Example 1 — small clean policy. Two Allow statements, no wildcards, well under every size limit → all size checks pass, 0 wildcard findings, 0 overly-permissive.

Example 2 — admin-style policy. A single statement with Action: "*" and Resource: "*" → 1 overly-permissive statement flagged, at least 2 high-risk wildcard findings.

Example 3 — large policy. A document whose whitespace-stripped JSON exceeds 2,048 characters → the user inline limit row shows a fail even though the managed-policy row may still pass.

• One dashboard instead of four separate tools for a first-pass read on a policy.
• Every number traceable to an existing, separately-documented analyzer — no new unverified logic.
• Catches size-limit problems early, before an attach/update call fails in the console or CLI.
• Private — everything stays in your browser.