Ultra-simple summary
👉 The order follows this logic:
1. Go to IAM
2. Define rules (Policy)
3. Organize (Groups)
4. Create user
5. Grant permissions
6. Secure (MFA)
7. Test
8. Apply to machines (Role)
1. Start by going into IAM (the “control
center”)
AWS Management Console
AWS Identity and Access Management
👉 Why?
Before creating users or giving access, you must go to the place
where everything is managed.
✔️ IAM = where you control who can do what in AWS
---
2. Create a GROUP (before the user)
👉 Why not create the user first ?
Because:
A group = a set of permissions
It avoids repeating the same permissions for each user
💡 Simple example:
➡️ “Admins” group → full access
➡️ “Developers” group → limited access
✔️ So: prepare the rules BEFORE adding people
---
3. Create a POLICY (the security rules)
👉 Why here?
Because:
A policy = permissions (allow / deny)
Without a policy → nobody can do anything
✔️ First define:
“What is allowed?”
---
4. Attach the policy to the group
👉 Why?
To avoid managing permissions user by user
✔️ Result:
➡️ The group is ready to use
➡️ All future users automatically get the permissions
---
5. Create the IAM user
👉 Why now?
Because:
You already prepared:
-the rules (policy)
-the structure (group)
✔️ So you can create a user cleanly and quickly
6. Add the user to the group
👉Why?
This is where the user gets permissions
✔️ Very important:
➡️ A user alone has NO permissions
➡️ The user inherits permissions from the group
---
7. Enable MFA (security)
👉 Why after creation?
Because:
MFA protects the account (two-factor authentication)
✔️ It’s an extra security layer
---
8. Test user login
👉 Why?
To verify that:
✔️ The user can log in
✔️ Everything works correctly
---
9. Test access denied
👉 Why?
To verify that security is working
✔️ Example:
➡️ The user tries a forbidden action
➡️ AWS should return: ACCESS DENIED
💡 Very important in cybersecurity!
---
10. Create an IAM role for EC2
Amazon EC2
👉 Why at the end?
Because:
Roles are for machines, not humans
It’s a more advanced concept
✔️ Example:
➡️ An EC2 instance accesses S3 without passwords
---
11. Tags + Review + Create
👉 Why?
Tags = organization (optional)
Review = avoid mistakes
Create = final step
---
12. Login + Credential Report
Why last?
The user can now log in
The report helps to:
✔️ check security
✔️ audit accounts
---
-Log in to AWS Management Console and Navigate to IAM :
-Creating an IAM Group :
-Creating a custom JSON Permission Policy :
-Attaching the policy to the group :
Step 2: Click on Users in the IAM Dashboard
Step 3: Click Add user
-Enabling MFA for an IAM user :
-Creating an IAM Role for EC2 (Permission granted to a machine) :
Copyright © All rights reserved.