Skip to content

AWS Certified Cloud Practitioner curriculum

Learn AWS cloud fundamentals through 12 real situations.

This is not a simplified copy of the Solutions Architect path. Each scenario is built around the business, security, service, cost, or support judgment the Cloud Practitioner exam expects.

12planned scenarios across 4 exam domains

A situation first

Begin with a company, constraint, or responsibility—not an AWS acronym.

Recognition in context

Learn what a service category is for and what nearby alternative it should not be confused with.

Available when reviewed

Planned lessons remain non-clickable until their content has been reviewed and published.

Stage 01 · Why cloud

Understand the value before the vocabulary.

Begin with business needs, global infrastructure, migration, and the Well-Architected mental model.

  1. 01

    Leave the Server Room

    Domain 1 · Cloud Concepts

    A growing company compares an on-premises refresh with moving workloads to AWS.

    • value proposition of AWS
    • fixed versus variable expense
    • elasticity
    • economies of scale
    Available
  2. 02

    Launch Globally Without New Data Centers

    Domain 3 · Cloud Technology and Services

    A product team needs low-latency access, resilience, and control over where customer data lives.

    • Regions
    • Availability Zones
    • edge locations
    • high availability
    Available
  3. 03

    Review a Cloud Design

    Domain 1 · Cloud Concepts

    A team evaluates a workload through the six AWS Well-Architected pillars instead of asking whether it merely works.

    • operational excellence
    • security
    • reliability
    • performance efficiency
    Available

Stage 02 · Responsibility and trust

Know who protects what—and how AWS earns trust.

Learn shared responsibility, identity, governance, compliance, and security evidence through realistic account decisions.

  1. 04

    Who Secures What?

    Domain 2 · Security and Compliance

    A team compares its security duties when it uses Amazon EC2, Amazon RDS, and AWS Lambda.

    • security of the cloud
    • security in the cloud
    • managed-service responsibility shifts
    • data protection
    Available
  2. 05

    Protect the AWS Account

    Domain 2 · Security and Compliance

    A new company replaces shared credentials with a defensible identity and access model.

    • root user protection
    • multi-factor authentication
    • least privilege
    • roles
    Available
  3. 06

    Prove Security and Compliance

    Domain 2 · Security and Compliance

    A regulated company must find AWS reports, protect data, and show what changed in its environment.

    • compliance evidence
    • encryption
    • auditing
    • configuration history
    Coming soon

Stage 03 · Services in context

Recognize the right category of AWS service.

Connect compute, storage, databases, networking, integration, analytics, and AI services to the situations they solve.

  1. 07

    Choose How the Application Runs

    Domain 3 · Cloud Technology and Services

    A small team compares virtual servers, containers, serverless functions, and simpler managed deployment options.

    • management responsibility
    • serverless
    • containers
    • automatic scaling
    Coming soon
  2. 08

    Choose Storage and Data Services

    Domain 3 · Cloud Technology and Services

    A business maps files, objects, disks, relational records, and key-value data to managed AWS services.

    • object, block, and file storage
    • storage classes
    • relational versus NoSQL
    • managed databases
    Coming soon
  3. 09

    Connect Users, Networks, and Locations

    Domain 3 · Cloud Technology and Services

    A company needs an isolated network, controlled traffic, reliable DNS, and a path back to its office.

    • Amazon VPC components
    • network security
    • DNS
    • content delivery
    Coming soon
  4. 10

    Turn Events and Data into Capabilities

    Domain 3 · Cloud Technology and Services

    A product team connects systems, analyzes business data, and recognizes when AWS AI, messaging, or business applications fit.

    • application integration
    • event-driven communication
    • analytics categories
    • AI and machine learning categories
    Coming soon

Stage 04 · Cost and help

Control spend and know where to get support.

Finish with purchase options, cost tools, consolidated billing, official resources, and AWS Support.

  1. 11

    Control a Growing AWS Bill

    Domain 4 · Billing, Pricing, and Support

    A finance and engineering team chooses purchase options, forecasts spend, and assigns costs across accounts.

    • On-Demand and Spot pricing
    • Savings Plans and reservations
    • data transfer pricing
    • forecasting
    Coming soon
  2. 12

    Choose the Right AWS Help

    Domain 4 · Billing, Pricing, and Support

    A team decides which support plan, health tool, expert, partner, or official knowledge source fits each problem.

    • AWS Support plans
    • service health
    • best-practice checks
    • official technical resources
    Coming soon