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 →
← Cloud Concepts: Well-Architected & Migration

Chapter 2 · Lesson 1 of 5

The six pillars of the Well-Architected Framework

1 min read

The AWS Well-Architected Framework is a set of best practices for designing and running workloads in the cloud, grouped into six pillars. Each pillar has design principles, and exam questions usually describe one principle in action and ask which pillar it belongs to.

PillarFocus and a typical principle
Operational excellenceRunning workloads well and improving processes: observability, frequent small reversible changes
SecurityProtecting data and systems: maintain traceability by logging and auditing every action
ReliabilityWorking correctly and recovering from failure: scale horizontally so one failure affects less
Performance efficiencyUsing resources efficiently to meet requirements: go global in minutes for lower latency
Cost optimizationBusiness value at the lowest price point: attribute spending, stop paying for undifferentiated heavy lifting
SustainabilityLowering environmental impact: maximize utilization so less energy is used per unit of work

Example: four hosts each running at 20% utilization are consolidated onto one host at 80%. If the stated goal is less energy per unit of work, the answer is sustainability, even though a smaller bill may follow.

If the stated goal were a lower bill, cost optimization would fit instead. Be wary of answers that say smaller or fewer servers always cost less or always use less energy, because neither is guaranteed.

Check yourself

1. A company consolidates two hosts, each running at 30% utilization, onto one host running at 60%. Its stated goal is to reduce the energy consumed per unit of work. Which pillar does this action serve?

2. A finance director wants each team's cloud spending attributed to that team, wants staff to stop paying for work that does not differentiate the business, and wants business value delivered at the lowest price point. Which Well-Architected pillar matches this goal?

Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) exam guide, AWS Well-Architected Framework, An Overview of the AWS Cloud Adoption Framework

AWS Cloud Practitioner cheat sheet: every key fact on one page →