AWS cloud
AWS IAM & multi-account security
IAM is the most-asked AWS security topic in DevOps interviews, and the one where vague answers are easiest to spot. A senior engineer must be able to read and write policies, explain how AWS evaluates them, set up roles for CI and Kubernetes workloads without long-lived keys, design a multi-account organisation with guardrails, and investigate an access-denied error or a leaked key methodically.
After this topic you can
- Write least-privilege IAM policies and roles
- Explain how a request is authorised, including SCPs and boundaries
- Set up a secure multi-account structure
Lessons
-
1Identities and credentials
- Principals
- STS and role assumption
-
2Policies: types and structure
- Policy document anatomy
- Policy types
- Policy evaluation logic
-
3Roles for workloads
- EC2, Lambda, ECS
- EKS: IRSA and Pod Identity
- CI/CD: OIDC federation
- Cross-account deploy roles
-
4Least privilege in practice
- Getting to least privilege
- ABAC (attribute-based access control)
- Permissions boundaries for delegation
- Privilege escalation paths to know
-
5AWS Organizations and multi-account strategy
- Why multiple accounts
- Typical structure (Control Tower / landing zone)
- Service Control Policies
- Identity Center (SSO)
-
6Detection, audit and incident response
- The detective stack
- Leaked access key — the runbook
- Debugging AccessDenied
-
7Interview questions and model answers
- "How does AWS evaluate whether a request is allowed?"
- "Role vs user?"
- "How does IRSA work?"
- "What are SCPs and what can't they do?"
- "How do you implement least privilege at scale?"
- "A developer's access key was found on a public GitHub repo. What do you do?"
- "Why use multiple AWS accounts?"
- "What's the confused deputy problem and how does External ID help?"