KMS key policies demystified
The lesson on key policies explained why our admin role could not decrypt objects. Very clear.
Browse
Read and write IAM policies with confidence, use roles, conditions, permission boundaries and Access Analyzer to grant only what each workload needs
Created by David Okafor
IAM is where AWS security succeeds or fails. Most teams know they should follow least privilege, but in practice permissions grow: a wildcard added to fix a deploy, a managed policy attached because it worked, an old access key nobody remembers creating. This course gives you a method for doing better without slowing your team down.
Each lesson starts from a realistic request, such as "the reporting job needs to read one bucket" or "contractors need read only access to staging", and we build the policy, test it with the policy simulator and the CLI, then try to break it. You will practise in your own account with resources that cost little or nothing.
Cloud engineer teaching AWS foundations and IAM with a security first, hands on approach
I design and run AWS accounts for small and mid sized engineering teams. Much of that work is unglamorous: tidy IAM policies, sensible networking, budgets and alarms that warn people before the bill does.
My teaching style is to build each concept in the console once so you can see it, then repeat it with the AWS CLI so you understand what the console did for you. I explain the why behind defaults, because most cloud incidents I have seen started with a default nobody questioned.
My courses stay inside the AWS Free Tier where possible and always end with a cleanup lesson, so you never get a surprise charge from practice resources.
The lesson on key policies explained why our admin role could not decrypt objects. Very clear.
I finally understand why adding permissions did not fix our AccessDenied errors. It was an SCP all along.
We replaced long term keys in GitHub Actions with OIDC the same week. The warning about loose subject conditions was important.
I had seen iam:PassRole in policies for years without understanding the risk. Now I review it carefully.
Lots of detail on conditions and boundaries. I needed to pause often, but everything was accurate and practical.
The checklist at the end is now part of our quarterly AWS review. More examples with Organizations would be welcome.
Good content, but it moves quickly if you have only used IAM through the console.