AWS Builder Center
Getting Started with AWS IAM: Users, Groups, and Policies

Getting Started with AWS IAM: Users, Groups, and Policies

A beginner friendly walkthrough of AWS IAM users, groups and policies and how they fit together.

Series: AWS Security 30 Days, 30 Articles Challenge (31 articles)

  1. …
  2. 3
    Getting Started with AWS IAM: Users, Groups, and Policies This article
Welcome to Day 2 of the 30 Days AWS Security Challenge. Yesterday we talked about who is responsible for what in AWS. Today we start on your side of that line with the service that controls almost everything else: IAM. If you get IAM right, a huge chunk of your security posture falls into place. Get it wrong, and everything downstream inherits the problem.

What IAM Actually Is

IAM stands for Identity and Access Management. It is the service that answers two questions for every single action taken in your AWS account: who is trying to do this, and are they allowed to?
Every time someone logs into the console, runs a CLI command, or an application calls an AWS API, IAM is checking credentials and permissions behind the scenes. Nothing happens in your account without passing through IAM first, which is exactly why it deserves attention this early in the challenge.

IAM Users: Individual Identities

A user in IAM represents a single person or application that needs access to your AWS account. Each user gets their own credentials, either a password for console access, access keys for programmatic access, or both.
A common mistake is treating IAM users like generic shared logins. Don't do this. Every real person or system that needs access should get their own user. That way, if something goes wrong, you can trace exactly who or what did it, and you can revoke one user's access without affecting anyone else.
To create a user in the console, go to IAM > Users > Create user, give it a name, and decide whether it needs console access, programmatic access, or both.

IAM Groups: Managing Permissions at Scale

Attaching permissions to individual users one by one works fine when you have three people. It falls apart fast when you have thirty. That is where groups come in.
A group is just a collection of users that share the same set of permissions. Instead of attaching a policy to each person on your data team, you attach it once to a "Data Team" group, then add and remove people from that group as they join or leave.
Some practical guidelines for using groups well:
  • Create groups around job function, like Developers, Admins, or Read-Only-Auditors
  • Attach policies to the group, not to individual users
  • Add or remove users from groups instead of editing permissions one by one
This keeps your permission structure predictable and much easier to audit later.

IAM Policies: The Actual Rules

Policies are where the real permission logic lives. A policy is a JSON document that spells out what actions are allowed or denied, on which AWS resources, and under what conditions. Users and groups don't have permissions by default. They only get permissions through attached policies.
A simple policy might allow a user to read objects from one specific S3 bucket and nothing else. AWS provides a set of ready made policies for common jobs, called AWS managed policies, and you can also write your own custom policies when you need finer control.
We will break down the actual JSON structure of a policy on Day 4, so don't worry if this part feels abstract right now. For today, just know that policies are the layer that turns "this user exists" into "this user can actually do these specific things."

Putting It Together: How Users, Groups, and Policies Work

Here is the mental model worth keeping:
  1. A user is an identity, a person or application
  1. A group is a way to organize users who need the same access
  1. A policy is the actual permission document that grants or denies specific actions
A user typically gets their permissions by belonging to one or more groups, each with policies attached. This layered structure is what lets you manage access for a growing team without permissions turning into chaos.

Key Takeaways

  • IAM controls who can do what in your AWS account, for every single action
  • Give every person and application its own IAM user, never share credentials
  • Use groups to manage permissions by job function instead of editing users one at a time
  • Policies are the JSON documents that actually define what is allowed
  • The combination of users, groups, and policies is the foundation for everything else you will secure in AWS
Tomorrow we go a level deeper and cover IAM roles, how they differ from users, and when you should reach for a role instead.

Series: AWS Security 30 Days, 30 Articles Challenge (31 articles)

  1. …
  2. 3
    Getting Started with AWS IAM: Users, Groups, and Policies This article
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article