Lesson 1 of 5
Create an AWS account and an IAM user
Create an AWS account and an IAM user with limited permissions, and see how this maps to identity services on Azure and Google Cloud.
4 minCloud
After this lesson, you will be able to create an AWS account, create an IAM user with limited permissions, and understand how this maps to identity services on Azure and Google Cloud.
Create an AWS account
Go to the AWS website and choose Create an AWS account. You need an email address, a password, and a payment method. AWS uses the payment method to verify your identity, but many services have a free tier for new accounts.
During sign-up, choose the Basic support plan. This plan is free and enough for this course. After you finish, sign in to the AWS Management Console as the root user. The root user has full access to everything in the account, so use it only for tasks that require it, such as changing your payment method.
Create an IAM user
For daily work, create an IAM user. IAM stands for Identity and Access Management. An IAM user is an identity with its own credentials, such as a password or access keys. You can give an IAM user only the permissions it needs, which reduces risk if the credentials are leaked.
In the AWS Management Console, search for IAM and open the IAM service. In the left menu, choose Users, then choose Create user.
Enter a user name, for example app-admin. Do not select Provide user access to the AWS Management Console yet, because this user will only use the command line in later lessons. Choose Next.
On the Set permissions page, choose Attach policies directly. A policy is a document that lists allowed actions. For this user, select the policy named AdministratorAccess. This policy allows all actions, which is too broad for production, but it is convenient for this course. In a later lesson, you will create a more limited policy. Choose Next, then Create user.
The next page shows the user's details. Choose the user name to open the user's page, then choose the Security credentials tab. Under Access keys, choose Create access key. Select Command Line Interface, tick the confirmation box, and choose Next. You can skip the description. Choose Create access key.
The page shows an Access key ID and a Secret access key. The secret key is shown only once. Download the .csv file or copy both values to a safe place. You will use these keys in a later lesson to configure the AWS CLI on your computer. Do not share them.
How this maps to Azure and Google Cloud
Azure and Google Cloud have similar identity services. In Azure, the equivalent of an AWS account is an Azure subscription. The equivalent of an IAM user is a user in Microsoft Entra ID, formerly Azure Active Directory. You assign permissions to users with Azure role-based access control, or Azure RBAC.
In Google Cloud, the equivalent of an AWS account is a Google Cloud project. The equivalent of an IAM user is a Google account or a service account. You assign permissions with Google Cloud IAM, which uses roles that are similar to AWS policies.
The idea is the same in all three clouds: create a separate identity for each person or application, and give it only the permissions it needs. This is called the principle of least privilege.
Secure your root user
Your AWS root user has full access to your account. Protect it with a strong password and multi-factor authentication, or MFA. MFA requires a second factor, such as a code from an app on your phone, in addition to your password.
In the AWS Management Console, click your account name at the top right, then choose Security credentials. Under Multi-factor authentication, choose Assign MFA. Follow the instructions to set up an authenticator app. After you set it up, sign out and sign in again to confirm it works.
From now on, use the IAM user for everyday tasks. Sign in to the console with the IAM user only if you selected console access earlier. If you did not, you can still use the IAM user's access keys for the command line, which is what later lessons require.
Key takeaways
- An AWS account is the top-level container for your resources, and the root user has full access.
- An IAM user is a separate identity with its own credentials, and you attach policies to grant permissions.
- Use the principle of least privilege: give each user only the permissions they need.
- Azure uses Microsoft Entra ID and Azure RBAC; Google Cloud uses Google accounts and Cloud IAM.
- Protect your root user with a strong password and MFA, and use IAM users for daily work.
Try it
Create an IAM user named test-user with the policy ReadOnlyAccess. This policy allows viewing resources but not changing them. After creating the user, create an access key for it. Then, in the IAM Users list, confirm that the user has the policy attached. A good result is that the user appears with the policy name ReadOnlyAccess in the Permissions tab, and you have saved the access key ID and secret key in a secure place.
Official documentation
Written with AI and checked automatically. Tools change, so a command may behave differently in the version you install. Spotted a mistake? Tell us.