AWS IAM — Policies, Roles, Permission Boundaries and SCPs — Cloud Security

AWS IAM is where the least-privilege principle from Module 1 becomes concrete machinery. Every request to AWS is evaluated against a stack of policies, and understanding how those policies combine is the difference between an account you can reason about and one that surprises you. This lesson covers the four instruments AWS gives you: identity policies, roles, permission boundaries, and Service Control Policies.

Analogy🏏Cricket

✈️ Think of it like travel: A modern airline does not inspect an aircraft once and trust it forever; a maintenance system continuously tracks every component, flags any part drifting out of tolerance, and surfaces the issue before the plane flies. Just as that system inventories every part and checks each against a standard so nothing is missed, CSPM inventories every cloud resource and checks each against best practice. Just as catching a worn part on the ground is far cheaper than discovering it aloft, catching a misconfiguration before an attacker does is far cheaper than after. This reveals why continuous automated checking is the natural defence against a constant risk.

These instruments operate at different layers and answer different questions. Identity policies grant what a principal may do. Roles let identities borrow permissions temporarily. Permission boundaries cap the maximum a principal can ever be given. Service Control Policies set an organisation-wide ceiling no account can exceed. Master how they interact and you can delegate freely without ever losing control of the outer limits.

Analogy🏏Cricket

🍳 Think of it like cooking: A busy restaurant kitchen changes minute by minute — pans go on and off the heat, orders fire, temperatures swing — and no single chef could watch every station at once, so kitchens run continuous checks with probe thermometers and timers. Just as the kitchen relies on constant monitoring because conditions shift too fast to inspect once, CSPM relies on continuous scanning because cloud configuration shifts too fast for a periodic review. Just as a dish safe at plating can spoil if left unwatched, a resource safe an hour ago can drift dangerous now. This reveals why relentless automated watching, not the occasional audit, keeps pace with the churn.