

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 2
click for more info
Not enough gems
Cost: 6 gems
1: Identity and Access Management (IAM)
incomplete
2: IAM Users
incomplete
3: Inline Policies
incomplete
4: IAM Groups
incomplete
5: IAM Roles
incomplete
6: Deny Policies
incomplete
7: SSM Parameters
incomplete
8: SSM Parameters Are Strings
incomplete
9: Accessing SSM Parameters from EC2
incomplete
10: Use SSM from EC2
incomplete
11: Cleanup
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
Let's make a new user! Each user gets a username/password or API keys to access AWS.
Users are long-lived identities: they stick around until you delete them. Once you create a user and give them credentials, those credentials will work until they expire or you revoke them.
Managing more than a handful of users manually is painful. If your company already uses something like Azure's Active Directory or Google Workspace, you can use AWS Identity Center to integrate with those services and manage users more easily.
HR just onboarded Vincent Vega to the PatientPing dev team! Definitely do not give him root access to the AWS account. Instead, start by giving him his own IAM user, with no console login or permissions yet. Standard corporate hygiene.
Create an IAM user named patientping-admin-vinny (no console access, no policies yet).
Cost check: Creating IAM users is free; costs arise from service usage (EC2, S3 etc.), not from IAM.
Run and submit the CLI tests.
Want to use the CLI instead? Here's the command structure:
aws iam create-user --user-name patientping-admin-vinny