IAM, or Identity and Access Management, decides who can do what in an AWS account. Most security problems in cloud projects start with permissions that are too broad.
The four building blocks
- User: a person or a service account that signs in.
- Group: a set of users with the same permissions.
- Role: permissions given temporarily to a service or a trusted account.
- Policy: a document that lists which actions are allowed or denied on which resources.
The rule to follow
Give only the permissions a task needs. Start with no access, then add the specific actions one by one. Avoid using the root account for everyday work.
A simple exercise
Create a user who can only read objects in one storage bucket. Test that the user can read the bucket and cannot delete anything in it.
Next step: see our cloud, AWS and DevOps course at ScholarLogic, or book a free demo class. A counsellor will share the fee and the next batch dates.
