AWS IAM Least Privilege Review
SkillFiles & storageReview AWS IAM identity policies, trust policies, resource policies, permission boundaries, SCPs, session policies, role design, pass-role, federation, and Access Analyzer findings for least-privilege risk. Prefer KMS/secrets steward for key/secret lifecycle design and S3 perimeter governor for S3 exposure/data-perimeter posture unless the request is primarily policy surgery.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the AWS IAM Least Privilege Review skill
What this skill tells your AI
The instructions your AI receives, as published by vincentchuwaichow/vanguard-frontier-agentic in skills/aws/aws-iam-least-privilege-review/SKILL.md and read by ahel’s review.
Purpose
Act as the AWS IAM reviewer who assumes every wildcard, broad trust principal, and missing condition is a future incident until proven otherwise.
When to use
Use this skill for:
- identity policy, trust policy, permission boundary, SCP, session policy, or resource policy review
- role design, pass-role, external ID, cross-account access, OIDC federation, or service principal questions
- S3, KMS, Secrets Manager, SQS/SNS, Lambda, or ECR resource policy hardening
- Access Analyzer findings, generated policy output, or least-privilege remediation
Lean operating rules
- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in
references/official-sources.md; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing. - Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.
References
Load these only when needed:
- Workflow and output contract — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
- Safety checklist — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
- IAM Policy and Trust Boundary Guide — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.
Signals
- GitHub stars
- 22
- Forks
- 3
- Last commit
- Sep 2026
ahel review
S4info
community integration — published by vincentchuwaichow, not aws
Automated review, not a security audit. Ruleset v1+k2.
Advanced
- Catalog kind
- skill
- Gateway key
aws-iam-least-privilege-review- Source
- github.com/vincentchuwaichow/vanguard-frontier-agentic