IAM Basics
Introduction
AWS Identity and Access Management (IAM) controls who can do what in your AWS account.
Before you can automate anything — CI/CD pipelines, Terraform deployments, model training jobs —
you need to understand how AWS decides whether to allow or deny an action.
Why This Matters
As a test automation engineer, you're used to running scripts with whatever permissions your
local machine has. In cloud environments, every action requires explicit permission.
Real-world scenario: Your CI/CD pipeline needs to push Docker images to ECR and deploy to EKS.
If you use your personal credentials (bad practice) and leave the company, everything breaks.
If you create an overly permissive role ("allow everything"), you've created a security risk.
Understanding IAM lets you give systems exactly the permissions they need — no more, no less.
This is called the Principle of Least Privilege, and it's fundamental to secure infrastructure.
Tasks
Hint: Search for 'IAM' in the AWS console search bar
Hint: Click on Users → your username → Permissions tab
Hint: aws s3 ls --profile test-automation-user