IAM Confused Me First, Then It Started Making Sense

Today I entered IAM, and it immediately felt like the place where AWS asks, ‘Who are you, and what are you allowed to do?’ That sounds simple, but the details branch quickly. Users, groups, roles, policies, permissions boundaries, managed policies, inline policies: IAM has a vocabulary that can slow a beginner down.

The hardest distinction was between a user and a role. A user felt easy: a person or long-term identity. A role felt abstract until I imagined temporary permission. A role is not a person; it is a trusted set of permissions that something can assume when needed.

The phrase ‘least privilege’ finally became practical. Instead of asking, ‘What permissions can I give?’ I should ask, ‘What is the smallest permission this task needs?’ That mindset changes IAM from a checkbox exercise into a safety habit.

I created a learning group idea, reviewed AWS managed policies, and read a simple JSON policy. The policy structure started to make sense: effect, action, resource, and optional conditions. It looked intimidating at first, but it is really a permission sentence written in JSON.

IAM is not a side topic. It is the layer that decides whether the rest of AWS is safe, chaotic, or usable.

Tomorrow I will create my first S3 bucket and use storage as the first real AWS service in this journey.