---
name: "aws-iam-least-privilege-policy"
description: "Author granular, least-privilege IAM policies and eliminate wildcards using IAM Access Analyzer."
metadata:
  author: "AWS"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "write least privilege iam policy"
  - "generate iam policy access analyzer"
  - "configure iam permission boundary"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# AWS IAM Least-Privilege Policies & Access Analyzer

Constructs AWS IAM policies: scoping Action, Resource, and Condition blocks (aws:PrincipalOrgID, s3:prefix), role assumption trust policies, detecting unused permissions with Access Analyzer, and permission boundaries.

## When to Invoke
Invoke this skill whenever you need to:
- write least privilege iam policy
- generate iam policy access analyzer
- configure iam permission boundary

## Execution SOP & Rules
1. Avoid Action: '*' and Resource: '*' wildcards; explicitly enumerate required API calls.
2. Use Condition blocks to enforce TLS (aws:SecureTransport: true) and IP CIDR restrictions.
3. Attach Permission Boundaries to developer roles to prevent privilege escalation.
4. Validate policy syntax with aws accessanalyzer validate-policy --policy-document file://policy.json.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.