π Working with IAM Users in AWS
In this lecture, we will practice using AWS Identity and Access Management (IAM) to create users inside your AWS account.
IAM is one of the most important services in AWS β and understanding it early will help you build secure architectures from day one.
π Accessing the IAM Console
Go to the AWS Management Console (AWS Dashboard which shown after login)
In the search bar, type IAM

π IAM is a Global Service
Once you're inside the IAM Dashboard, notice something very important.
If you look at the top-right corner, youβll see that the region selector is disabled.

That means:
There is no region selection
Users you create are available across all AWS regions
Permissions apply account-wide
β οΈ This is different from services like EC2 or S3, which are region-specific.
π€ Why Do We Create IAM Users?
Right now, you are logged in as the root user (account owner).
β You can confirm this because:
You see your Account ID ( IAM user does not have their own Account ID)
You logged in using the root credentials

π Best Practice:
Never use the root account for daily activities.
Create IAM users. Grant them appropriate permissions
Use them for regular access. This significantly improves your account security.
π Creating an IAM User
1. In the left sidebar, click Users or IAM users

2. Click Create user

3. Specify User Details
Enter a User name (example:
codeveda)Enable Provide user access to the AWS Management Console

Click Next
Beginners often mix these up:
β
Authentication β Can the user log in?
β Authorization β What can the user do once logged in?
Turning on console access only lets a user log in. It doesn't give them any permissions.
π To grant access to specific things, you need to attach IAM policies.
Without any policies attached, the user will hit "Access Denied" on almost everything.
4. Setting the Password
π² Auto-generated password
βοΈ Custom password
π² Keep auto-generated enabled
π Turn on "Require password reset at next sign-in"
βοΈ Choose a custom password
βοΈ You can uncheck "Require password reset"

Click Next
5. Set Permissions
Now assign permissions. You have three options:
Attach policies directly β Permissions apply only to this user. Simple, but hard to manage at scale.
Add user to a group β Permissions come from the group. Easiest to manage as your team grows.
Copy permissions from another user β Duplicates an existing user's permissions onto this one. Quick, but you inherit their exact setup, including anything outdated.
π Best practice: Use groups
.π₯ Creating an Admin Group
Click Create group
Group name:
AdminAttach policy: AdministratorAccess (This policy grants full access to AWS)
Add the user to the Admin group
Click Next
6. Review and Create
βΌοΈ Review your configuration carefully
π€ User name β codeveda
π Console password β Custom
π Require password reset β No
π₯ Group β Admin
π Policy β AdministratorAccess
π·οΈ Key β department
π·οΈ Value β technology
π Tags are key-value metadata pairs that help you organize and identify AWS resources.
Click Create user
7. Retrieve the Password
This is the only time you can download or view the password (if auto-generated).
Options:
Download CSV
Email sign-in instructions

β οΈ If you lose this password, you must reset it manually.
π₯ Understanding Permission Inheritance
If you open User Groups, you'll see a group called Admins β and inside it, one user: codeveda.
Check the group's permissions, and you'll find AdministratorAccess attached there.
Now check the user codeveda directly β it also shows AdministratorAccess. But it's not attached to the user. It's inherited from the group.
In short:
π₯ Any permission attached to a group
β‘ Automatically applies to every user inside that group
π Signing in as the IAM User
Now letβs log in using the new IAM user. But before that, Go to π

Your IAM Dashboard
Creating an Account Alias
You can customize the sign-in URL by creating an account alias.
It must be unique globally.
π‘ This URL can be used by all IAM users for quick and easy login, so they donβt need to remember the account ID or account alias.
π₯ Using Two Browser Windows
Recommended approach:
Left window β Root user (normal browser)
Right window β IAM user (private/incognito mode)
π This allows you to:
Compare permissions
Use two identities simultaneously
If you log into both in the same browser session, one session will replace the other.
Check the top-right corner:
You should now see IAM user β
codevedaAccount ID displayed
No longer logged in as root
β οΈ Critical Security Note
π Do NOT lose:
Root account credentials
Admin IAM credentials
If you lose both, account recovery becomes very complex and requires contacting AWS Support.
π Course Recommendation
For this course:
β Use your IAM user for daily work
β Avoid using root unless explicitly required
Sometimes I may demonstrate actions using root, but I will clearly mention when that is necessary.
For now:
Keep both windows open
Make sure you understand the difference between root and IAM user access