Originally published at unifiedpathmedia.com .
The short version: IAM (Identity and Access Management) decides who, or what, can do what in your AWS (Amazon Web Services) account. Get its building blocks straight early and you dodge both classic failure modes. One is permissions that are too loose (a security hole). The other is permissions so tight that everyone gives up and grants admin to everything (the same security hole, wearing a disguise). The essentials: users vs. groups vs. roles, why roles beat hardcoded keys, and least privilege in practice.
← Part of the AWS Foundations series
Published September 2, 2026.
Last verified November 5, 2026 against the AWS IAM User Guide (identities, policies and the policy simulator).
Who this is for: anyone who has secured the root user and now needs to decide who can do what. You’ll need first: a locked-down account from Part 1 .
IAM is the bouncer for your AWS account: it checks who’s allowed to do what, everywhere, all the time.…