Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/41 ▾
  1. 1.Cloud Concepts: Benefits & Economics0/4
    1. The six advantages of cloud computing
    2. Elasticity, scalability, agility, high availability and global reach
    3. Cloud economics: fixed versus variable cost and total cost of ownership
    4. Licensing, rightsizing and automation
  2. 2.Cloud Concepts: Well-Architected & Migration0/5
    1. The six pillars of the Well-Architected Framework
    2. Pillar trade-offs and the AWS Well-Architected Tool
    3. The AWS Cloud Adoption Framework: outcomes, perspectives and phases
    4. Migration strategies: the 7 Rs
    5. AWS migration services and tools
  3. 3.Security: Shared Responsibility & Compliance0/4
    1. Security of the cloud and security in the cloud
    2. How responsibility shifts with the service you choose
    3. Compliance reports, programs and where data lives
    4. Encryption, keys and audit records
  4. 4.Security: IAM & Access Management0/4
    1. The root user and sign-in credentials
    2. IAM users, user groups and roles
    3. Policies, deny rules and least privilege
    4. Federation, IAM Identity Center, Amazon Cognito and secrets
  5. 5.Security: Services & Resources0/4
    1. Blocking web attacks and DDoS: AWS WAF, AWS Shield and AWS Firewall Manager
    2. Detecting threats, flaws and sensitive data: GuardDuty, Inspector and Macie
    3. Collecting, investigating and advising: Security Hub, Detective and Trusted Advisor
    4. AWS Marketplace and where to find security help
  6. 6.Technology: Deployment & Global Infrastructure0/4
    1. Ways to access AWS: console, CLI, SDKs and APIs
    2. Deployment tools and cloud deployment models
    3. Regions, Availability Zones and high availability
    4. Multiple Regions, data residency and edge services
  7. 7.Technology: Compute & Networking0/4
    1. Amazon EC2 instance types, auto scaling and load balancers
    2. Containers, serverless compute, Lightsail and AWS Batch
    3. Inside a VPC: subnets, gateways, security groups and network ACLs
    4. Route 53 and connecting networks to AWS
  8. 8.Technology: Databases & Storage0/4
    1. Relational databases: Amazon RDS, Aurora and databases on EC2
    2. NoSQL, in-memory and graph databases, plus database migration
    3. Amazon S3 object storage, storage classes and lifecycle policies
    4. Block and file storage, Storage Gateway, AWS Backup and disaster recovery
  9. 9.Technology: AI, Analytics & Other Services0/4
    1. AI and machine learning services: pre-trained services and SageMaker AI
    2. Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
    3. Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
    4. Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
  10. 10.Billing, Pricing & Support0/4
    1. EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
    2. Data transfer costs, consolidated billing and cost allocation tags
    3. Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
    4. AWS Support plans, Trusted Advisor, AWS Health and where to get help
Saved in this browser. Move it to another device →
← Security: IAM & Access Management

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 →