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 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.
| Pillar | Focus and a typical principle |
|---|---|
| Operational excellence | Running workloads well and improving processes: observability, frequent small reversible changes |
| Security | Protecting data and systems: maintain traceability by logging and auditing every action |
| Reliability | Working correctly and recovering from failure: scale horizontally so one failure affects less |
| Performance efficiency | Using resources efficiently to meet requirements: go global in minutes for lower latency |
| Cost optimization | Business value at the lowest price point: attribute spending, stop paying for undifferentiated heavy lifting |
| Sustainability | Lowering 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 →