AWS Builder Center
šŸ” AWS IAM Explained for Beginners: Users, Roles, Policies & MFA

šŸ” AWS IAM Explained for Beginners: Users, Roles, Policies & MFA

Starting AWS but confused about IAM? In this beginner-friendly guide, I explain AWS IAM, Users, Groups, Roles, Policies, and MFA in simple terms, with practical examples to help new AWS learners understand how AWS access and security work.

šŸ” Starting AWS but confused about IAM?

When I first started exploring AWS, I came across terms like Users, Groups, Roles, Policies, and MFA.
At first, they all seemed similar.
Who gets access? Who gives permission? What is a role? Why do we need policies? And what exactly does MFA do?
So in this article, I'll explain AWS Identity and Access Management (IAM) in a simple way for students and beginners who are starting their AWS journey.



ā˜ļø What is AWS IAM?

AWS Identity and Access Management (IAM) is a service that helps you control who can access AWS resources and what they are allowed to do.
For example, imagine you have an AWS account containing:
AWS Account
│
ā”œā”€ā”€ S3
ā”œā”€ā”€ EC2
ā”œā”€ā”€ Lambda
ā”œā”€ā”€ DynamoDB
└── Other AWS Services
You don't want everyone to have permission to access everything.
IAM allows you to control access.
A simple way to remember it is:
IAM = Who can access what, and what can they do?



šŸ‘¤ 1. IAM User — "Who are you?"

An IAM User represents an individual identity that can have AWS permissions.
For example, imagine a company has:
AWS Account
│
ā”œā”€ā”€ Mahesh
ā”œā”€ā”€ Rahul
└── Priya
Each person can have different permissions.
For example:
Mahesh
→ Can work with S3
Rahul
→ Can work with EC2
Priya
→ Can manage billing
The important idea is:
User = an identity that represents a person or application that needs long-term access.



šŸ‘„ 2. IAM Group — "Which users belong together?"

Instead of giving permissions to every user individually, you can organize users into Groups.
For example:
Developers Group
│
ā”œā”€ā”€ Mahesh
ā”œā”€ā”€ Rahul
└── Priya
You can attach appropriate permissions to the group.
All users in that group can receive the group's permissions.
For example:
Developers
↓
S3 + Lambda permissions
↓
Mahesh
Rahul
Priya
This makes permission management easier when you have many users.

Easy way to remember:

Group = collection of IAM users



šŸ“œ 3. IAM Policy — "What are you allowed to do?"

This is one of the most important IAM concepts.
An IAM Policy is a document that defines permissions.
For example, a policy could say:
This user can read objects from a particular S3 bucket.
Or:
This role can invoke a Lambda function.
Think of a policy as a permission rulebook.
IAM Policy
↓
What action?
↓
On which resource?
↓
Allow or Deny?
A policy can control things such as:
  • What action can be performed
  • Which AWS resource it applies to
  • Whether the action is allowed or denied

Simple example

Imagine you have an S3 bucket:
my-student-project
You could create permissions that allow someone to:
Read → ALLOW
Upload → ALLOW
Delete → DENY
So they can work with the project without being able to delete everything.



šŸŽ­ 4. IAM Role — "What permissions can you temporarily assume?"

This is where many beginners get confused.
An IAM Role is different from an IAM User.
A role is designed to be assumed by a trusted entity and provides temporary credentials.
For example, imagine you have an application running on EC2.
Your application needs to read files from S3.
Instead of storing AWS access keys inside your application, you can give the EC2 instance an IAM Role.
EC2
│
│ assumes
↓
IAM Role
│
│ has
↓
S3 Permissions
Now the application can access the required S3 resources through the role.

Why is this useful?

It avoids putting long-term AWS credentials directly inside your application.

Easy way to remember:

User = identity Role = permissions that can be assumed



šŸ” 5. MFA — Extra Security

MFA = Multi-Factor Authentication
A password is one authentication factor.
MFA adds another factor.
For example:
Password
+
Authenticator / Security Key
=
MFA
Even if someone somehow gets your password, they may still need the second authentication factor.
For AWS accounts, MFA is an important security measure.

Simple example

Without MFA:
Password
↓
Login
With MFA:
Password
↓
MFA verification
↓
Login
This provides an additional layer of protection.



🧠 Users vs Groups vs Policies vs Roles

Here's the easiest way I remember them:
IAM Component
Simple meaning
šŸ‘¤ User
Who you are
šŸ‘„ Group
Users grouped together
šŸ“œ Policy
What you're allowed to do
šŸŽ­ Role
Permissions that can be assumed
šŸ” MFA
Additional authentication/security
Remember:
User → Group → Policy Role → Temporary access MFA → Extra security



šŸ—ļø A Simple Real-World Example

Imagine we're building an AI application.
The application is running on EC2 and stores images in S3.
We could have:
AWS Account
│
ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”“ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│ │
IAM Resources
│ │
ā”Œā”€ā”€ā”€ā”€ā”“ā”€ā”€ā”€ā”€ā” ā”Œā”€ā”€ā”€ā”€ā”“ā”€ā”€ā”€ā”€ā”€ā”
│ │ │ │
Users Roles EC2 S3
│ │ │
Groups Policies │
│ │
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜
The EC2 instance can assume a role that gives it only the S3 permissions it actually needs.
This follows an important security principle:

šŸ”‘ Least Privilege

Give only the permissions that are necessary.
If an application only needs to read from S3, don't give it permission to delete every object in the account.



āš ļø Common Beginner Mistakes

When starting AWS, it's easy to make mistakes with IAM.

āŒ Giving everyone administrator permissions

Not everyone needs full access.

āŒ Storing AWS access keys inside source code

Avoid putting credentials directly into your application code.

āŒ Ignoring MFA

Especially for important AWS accounts.

āŒ Giving more permissions than necessary

Always think about least privilege.

āŒ Using the root user for everyday tasks

The root user has extremely powerful permissions, so it should be protected carefully and not used for normal day-to-day work.



šŸ¤– Why IAM Matters for AI/ML Students

As an AI/ML student, you may eventually build applications using:
Python + AI/ML + AWS
For example:
User
↓
Web Application
↓
API
↓
Lambda / EC2
↓
AI Service
↓
S3 / DynamoDB
Different components may need different permissions.
IAM helps control those permissions.
So understanding IAM isn't only useful for passing an AWS certification exam.
It becomes important when you're actually deploying applications to AWS.



šŸŽÆ What I'm Learning Next

I'm currently continuing my AWS learning journey and exploring services such as:
  • Amazon S3
  • Amazon EC2
  • AWS Lambda
  • Amazon DynamoDB
  • IAM
My goal is to understand how these services can work together to build real-world applications, especially applications involving AI/ML and cloud computing.



šŸ’¬ Let's Learn Together!

If you're also learning AWS, I'd love to hear from you.

Which IAM concept was the most confusing when you started?

1ļøāƒ£ Users 2ļøāƒ£ Groups 3ļøāƒ£ Policies 4ļøāƒ£ Roles 5ļøāƒ£ MFA
Or if you've already used IAM in a project, what did you use it for?
Share your experience in the comments. I'll try to read and reply to every genuine comment so we can learn from each other. šŸ¤
If you're also participating in AWS Student Rewards, feel free to share your progress and learning articles below.
Let's continue:
Learn → Build → Share → Discuss → Grow šŸš€
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