The AWS Well-Architected Framework
Identify design principles of the AWS Well-Architected Framework
What you will learn
- Name the six pillars of the AWS Well-Architected Framework and what each one measures.
- Distinguish the Framework as guidance from the AWS Well-Architected Tool as an actual account service.
- Trace the steps of using the tool to review a real, existing workload.
- Recall that the Sustainability pillar was added later, not one of the original four.
The AWS Well-Architected Framework is not a service you buy — it is a set of questions and recommended practices AWS publishes to help you evaluate any cloud workload from six different angles. The core idea: a system that works is not the same as a system that is well designed. It might work and still be needlessly expensive, fragile against one component failing, or unable to scale later.
The six pillars
| Operational Excellence | Running, monitoring, and continuously improving systems through automated procedures rather than repeated manual intervention. |
|---|---|
| Security | Protecting information and systems through identity and access management, data protection, and detecting and responding to events. |
| Reliability | A system's ability to recover automatically from infrastructure or service failure and meet demand without unplanned outages. |
| Performance Efficiency | Using computing resources efficiently to match actual demand, and maintaining that efficiency as demand and technologies change. |
| Cost Optimization | Achieving the business outcome at the lowest possible cost, by tracking spend and choosing the right pricing model and resources. |
| Sustainability | Minimizing the environmental impact of running the workload — the sixth pillar, officially added in December 2021. |
The Framework vs. the Tool
| AWS Well-Architected Framework | AWS Well-Architected Tool | |
|---|---|---|
| What it is | General guidance — recommended questions and practices | An actual service inside your AWS account |
| Cost | Not directly used — just reading material | Completely free |
| Output | General principles and concepts | An actual risk report for a specific, named workload in your account |
How the tool is used
Define the workload
Name it and specify its environment (production, test...).
Answer each pillar's questions
Yes/no questions about practices actually applied to the workload.
Review the resulting risks
The tool classifies each negative answer as a high, medium, or low risk.
Apply the recommended improvements
Direct links to the relevant AWS documentation for each risk.
What matters on the exam
- The exam asks about the six pillars' names and general meaning — not deep technical detail within each.
- The tool is free, and its output is a risk report, not an official compliance certificate.
- The pillars have no mandatory ranking — none is absolutely "most important"; priority depends on the workload itself.
Sustainability is the newest
If you see a claim that the Framework was born with six pillars from day one, it is historically inaccurate — it started smaller, and Sustainability was the last one added, in 2021, becoming the sixth. This history is rarely tested directly, but it explains why Sustainability is sometimes the one left off a memorized list.
Quick check
Answer in your head first, then reveal.
How many pillars does the AWS Well-Architected Framework have?Reveal the answer
Six.
What is the core difference between the Framework and the Tool?Reveal the answer
The Framework is general guidance; the Tool is an actual service reviewing a specific workload in your account.
Which pillar concerns reducing environmental impact?Reveal the answer
Sustainability.
Does using the AWS Well-Architected Tool cost anything?Reveal the answer
No, the tool is completely free.
Sign in to track your progress on this topic.
Your next step
Read the lesson, then mark it complete
Sources
Used to verify the facts. The writing is original to Passuit.