AWS Beginner: AWS is different. What are AWS Accounts, IAM Users and Root User?
The AWS account setup is different from other services. There are accounts, IAM users and a root user. But what are the differences?
4 min read
Things are confusing when you are just starting to use AWS. You don't just create an account and get started as you do with other services. You come across terms like "Account", "User" and "Root User" and maybe ask yourself how they differ. This post should help understand these terms.
When You Sign Up for an AWS Account
If you sign up for an AWS account you will be asked to enter a "Root user email address" and an "AWS account name":
After you finish the signup process, you will end up with an account (identified by a 12-digit account ID and an account name, also known as account alias) and some credentials (email and password of your root user) to enter that account.
This is what the AWS docs say about the root user in a red warning callout:
We strongly recommend that you do not use the root user for your everyday tasks, even the administrative ones. Instead, adhere to the best practice of using the root user only to create your first IAM user.
Okay, so you should create an IAM user (often just referred to as user; this is how you can create an IAM user) but what is the difference between an IAM user and the root user? And usually, if you sign up for a service you create an account with credentials and end up with one thing: an account. Why do you have (at least) three account-related things in AWS? How are they different? Before we will get to the definitions we will have a look at how to sign in using either the root user or an IAM user.
Sign In to your account
This is how the sign-in screen looks like when you click on the "Sign In" button on https://aws.amazon.com/console/:
You can either go ahead and sign in as a root user by just providing the root user email address and the password or you can sign in as an IAM user by providing the account ID or account alias first and the IAM user name and password in the second step:
Note how you don't have to provide the account ID for the root user as that user has to be unique globally.
Also, you can use your account name in a URL like https://myaccountname.signin.aws.amazon.com/console to populate the account id input with
myaccountname (that account alias must exist, otherwise you will land on a 404 page).
Now let's get to the definitions.
Think of an account as just a container. A container containing your resources, users and account settings.
You can create multiple of these containers. In fact, it is best practice to separate your different workloads (for example test and production) into different accounts.
The root user is the master of your account. It is the central key (this is why you should activate Multi-Factor Authentication (MFA) for it) and provides unrestricted access to the account. There is always exactly one root user per account.
There are some tasks that only a root user can do, e.g. changing the account settings (including the account name) and billing information.
Again: use MFA for your root user and only use that user if you have to, don't use it for everyday work.
An IAM User is an entity representing a person or an application (it is not necessarily a person, this can be confusing because the word "user" implies a person). You create the IAM users after the initial creation of your root user. An account can have several users (think of people or applications being able to access the container of resources).
There are various ways how you can grant IAM users permissions in order to be able to do something. One of them is attaching policies to the IAM user ([learn more about IAM permissions](permissions for an IAM user)). An IAM user with the
AdministratorAccess policy attached is not the same as the root user.
The concept of accounts and users in AWS is different from what we are used to (Google, Spotify, etc.). This can lead to confusion. Hopefully this post has cleared up that confusion for you.
If you need help getting going, feel free to ask questions.
Did you find this article valuable?
Support Jannik Wempe by becoming a sponsor. Any amount is appreciated!