Aws Iam
AWS IAM deep-dive skill - principal types, policy evaluation, STS assume role, SCP guardrails, KMS key policies/grants, and AccessDenied debugging. Use when designing AWS authz/authn, cross-account access, or troubleshooting IAM/KMS/SCP AccessDenied errors.
Install
$ agentstack add skill-d-padmanabhan-agent-engineering-handbook-aws-iam ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-d-padmanabhan-agent-engineering-handbook-aws-iam) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
AWS IAM
When to use
Use this skill when you are working on:
- IAM principals (users, roles, assumed-role sessions, service principals)
- Trust policies (
sts:AssumeRole*) and cross-account access - Identity-based vs resource-based policies
- Permission boundaries, session policies, and Organizations SCPs
- KMS key policies, grants, and
kms:Decrypt/kms:GenerateDataKeyfailures - Debugging
AccessDeniedin AWS (including cross-account and KMS)
What to do (workflow)
- Identify the runtime principal (often an STS assumed-role ARN)
- Identify the action + resource ARN(s) from the error or design requirement
- Determine which policy layers are in play:
- identity-based policy
- resource-based policy
- permission boundary
- session policy
- SCP (Organizations)
- Look for explicit deny first (it wins)
- For cross-account flows:
- validate the trust policy (who can assume)
- validate the permission policy (what the role can do)
- validate any resource policy (who can access the target resource)
- For KMS:
- validate key policy + IAM policy + any grant constraints
References
references/iam-authorization-model.mdreferences/cross-account-and-externalid.mdreferences/cross-service-confused-deputy.mdreferences/kms-key-policy-and-grants.mdreferences/eks-pod-identity-abac-and-lattice.md
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: d-padmanabhan
- Source: d-padmanabhan/agent-engineering-handbook
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.