Chapters0/41 ▾
- 1.Cloud Concepts: Benefits & Economics0/4
- 2.Cloud Concepts: Well-Architected & Migration0/5
- 3.Security: Shared Responsibility & Compliance0/4
- 4.Security: IAM & Access Management0/4
- 5.Security: Services & Resources0/4
- 6.Technology: Deployment & Global Infrastructure0/4
- 7.Technology: Compute & Networking0/4
- 8.Technology: Databases & Storage0/4
- 9.Technology: AI, Analytics & Other Services0/4
- AI and machine learning services: pre-trained services and SageMaker AI
- Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
- Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
- Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
- 10.Billing, Pricing & Support0/4
- EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
- Data transfer costs, consolidated billing and cost allocation tags
- Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
- AWS Support plans, Trusted Advisor, AWS Health and where to get help
Chapter 4 · Lesson 1 of 4
The root user and sign-in credentials
1 min read
Every AWS account starts with a root user, the identity tied to the account's sign-in email, and it has complete access to everything in the account. AWS recommends securing it first: turn on multi-factor authentication (MFA), create no access keys for root, never share its password, and set up a separate administrative identity for daily work.
Root is kept for the rare tasks that only it can do. In a standalone account outside AWS Organizations, those include closing the account and changing the root sign-in email. Creating IAM administrators, listing users and updating alternate contacts can all be done by IAM identities with the right permissions.
- Strongest MFA: passkeys and FIDO security keys resist phishing because they respond only to the real AWS site. A six-digit code from an app or token can be typed into a fake site.
- The IAM account password policy applies only to IAM users' passwords, not to the root user's password or to any access keys.
- An access key pairs an access key ID with a secret access key. The secret is shown only once, at creation, so a lost secret means deleting the key and creating a new one.
Example: a two-person startup has just opened an account. Before anything else, the founder adds a security key as MFA on root, creates an administrator identity for each founder, signs out of root, and stores the root credentials somewhere safe.
Check yourself
1. A small company has just opened an AWS account and signed in as the root user. What should it do before starting everyday administration?
2. In a standalone AWS account that is not part of AWS Organizations, which task can only the root user perform?
Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, IAM User Guide: Security best practices in IAM, AWS IAM Identity Center User Guide
AWS Cloud Practitioner cheat sheet: every key fact on one page →