The AWS Well-Architected Framework is a consistent set of best practices and questions for evaluating architectures. The AWS Well-Architected Tool runs those reviews for your workloads.
The six pillars
The AWS Well-Architected Framework is AWS’s set of best practices for cloud architectures. It is organized in six pillars and comes with questions that show how well a workload follows them.
How it works
- Pick a workload: a set of components that together deliver business value.
- Review it against each pillar’s questions and best practices.
- Fix the risks the review finds, starting with the highest.
- Repeat as the workload changes; the framework treats architecture as something that evolves.
| Pillar | Focus |
|---|---|
| Security | Protect data, systems and assets |
| Reliability | Perform the intended function correctly and consistently |
| Cost optimization | Deliver business value at the lowest price point |
The other pillars are operational excellence, performance efficiency and sustainability.
Since November 16, 2026, the framework is one document in two parts. Cloud Foundations covers what an organization sets up once for all workloads (accounts, identity, observability, inventory, security, cost, networking), and Cloud Workloads holds the six pillars.
The general design principles apply across pillars: stop guessing capacity, test at production scale, automate to experiment, evolve the architecture, decide with data, and improve through game days.
Exam cues
- If the question says recover from failure or work consistently, think reliability.
- If the question says lowest price point for the value delivered, think cost optimization.
- If the question says protect data, systems and assets, think security.
- If the question says simulate production events to find improvements, think game days.
- If the question says reduce dependencies between components, think loosely coupled dependencies under reliability.
- If the question says organization-wide setup before the first workload, such as a landing zone, think Well-Architected Cloud Foundations.
Remember
- Six pillars; sustainability is the sixth.
- November 16, 2026: one framework document, split into Cloud Foundations (seven capabilities) and Cloud Workloads (the pillars).
- A workload is a set of components that deliver business value.
- Game days simulate production events to practice handling them.
Trap: Reliability includes both performing the intended function consistently and testing recovery procedures.
From the AWS docs (14)
- The AWS Well-Architected Framework provides a consistent set of best practices for evaluating architectures and a set of questions to check how well an architecture aligns with AWS best practices.
- The framework has six pillars: operational excellence, security, reliability, performance efficiency, cost optimization and sustainability.
- The security pillar describes how to use cloud technologies to protect data, systems and assets in a way that improves security posture.
- Reliability is the ability of a workload to perform its intended function correctly and consistently when expected, including operating and testing it through its total lifecycle.
- Cost optimization is the ability to run systems that deliver business value at the lowest price point.
- In the framework, a workload is a set of components that together deliver business value.
- The general design principles are to stop guessing capacity needs, test systems at production scale, automate with architectural experimentation in mind, consider evolutionary architectures, drive architectures using data, and improve through game days.
- Game days simulate events in production on a regular schedule to find improvements and build experience in handling events.
- The reliability pillar recommends loosely coupled dependencies, such as queues, streams and workflows, ideally asynchronous; a monolithic workload is an anti-pattern.
- Reliability pillar design principles: automatically recover from failure, test recovery procedures, scale horizontally to increase aggregate workload availability, stop guessing capacity, and manage change through automation.
- On November 16, 2026, AWS consolidated the six pillar whitepapers into one Well-Architected Framework document, refreshed nearly all best practices, and split the guidance into Cloud Foundations and Cloud Workloads.
- Well-Architected Cloud Foundations covers organization-wide capabilities to set up before production workloads, in seven areas: multi-account environment, identity and access management, central observability, resource and inventory management, security and compliance, cloud financial management, and networking and connectivity.
- AWS describes Well-Architected Cloud Foundations as the blueprint for a sound landing zone, a well-architected multi-account AWS environment.
- Cloud Workloads holds the six pillars and their workload best practices, which can be evaluated and tracked continually.
Well-Architected Tool
The AWS Well-Architected Tool runs Well-Architected Framework reviews in the AWS console. You answer the questions for a workload, and the tool lists the risks and an improvement plan.
How it works
- Define a workload in the tool.
- Answer the review questions for each pillar. Lenses supply the questions; custom lenses add your own.
- Read the result: high risk issues (HRIs), medium risk issues (MRIs) and an improvement plan.
- Save a milestone, make improvements, and review again to track progress.
AWS Well-Architected Agent, in preview as of October 2026, takes another approach: it analyzes deployed resources with AI and proposes fixes. The two can be used together.
Exam cues
- If the question says review a workload against AWS best practices, think AWS Well-Architected Tool.
- If the question says add company-specific best practices to reviews, think custom lenses.
- If the question says track improvement over time, think milestones.
- If the question says measure the carbon emissions of AWS usage, think the AWS Sustainability console, because it estimates emissions by Region and service.
Remember
- The tool documents decisions and risks; it does not change resources.
- Results: high and medium risk issues plus an improvement plan.
Trap: The Well-Architected Tool is not AWS Trusted Advisor. Trusted Advisor runs automated checks on your account; the WA Tool guides a review of a workload’s design.
From the AWS docs (8)
- The AWS Well-Architected Tool provides a consistent process for measuring an architecture against AWS best practices from the Well-Architected Framework.
- The tool helps document decisions, recommends improvements based on best practices, and guides workloads toward being more reliable, secure, efficient and cost-effective.
- Custom lenses let you measure a workload against your own best practices, with questions specific to a technology or to your governance needs.
- A Well-Architected Tool review is a guided self-review that produces identified risks (high and medium risk issues) and an improvement plan; milestones track progress over time.
- AWS Well-Architected Agent, in preview as of October 2026, analyzes deployed resources and IaC templates with AI and returns prioritized recommendations, automation scripts and updated templates.
- Customers use the tool to document architectures, provide product launch governance, and understand and manage the risks in their technology portfolio.
- The AWS Sustainability console shows the estimated carbon emissions and water allocation from an account's AWS usage, broken down by AWS Region, service and, for emissions, scope; data for each month is published the following month.
- Signed in to an AWS Organizations management account, AWS Sustainability reports the consolidated impact of the member accounts; a member account sees only its own data.
Pillar design principles
The AWS Well-Architected pillars address different aspects of a workload, from running it effectively to using resources efficiently and reducing its environmental impact. Their design principles help teams identify practices for each goal.
How it works
- For operational excellence, define the workload and its operations as code and automate procedures safely. Make small, reversible changes and anticipate failure.
- For security, maintain traceability and keep people away from data. Other principles include a strong identity foundation and protection for data in transit and at rest.
- For performance efficiency, deploy closer to customers and consider mechanical sympathy: choose technology that fits the workload’s needs.
- For cost optimization, measure business outcomes against costs and allocate costs at a granular level.
- For sustainability, increase resource utilization and reduce the footprint of data and its processing.
Exam cues
- If the question says improve procedures and learn from operations, think operational excellence, because it focuses on running workloads effectively and improving operations.
- If the question says keep computing resources efficient as demand changes, think performance efficiency, because it addresses efficiency as requirements and technology change.
- If the question says deliver business value at the lowest price point, think cost optimization, because its goal includes both value and cost.
- If the question says reduce energy consumption and resources, think sustainability, because it focuses on reducing environmental impact.
- If the question says trace actions or keep people away from data, think security, because both are security design principles.
- If the question says test at production scale without keeping the environment running, think create it on demand and decommission it after testing. You pay while it runs.
Remember
- Operations as code and frequent, small, reversible changes are operational excellence principles.
- Deploying closer to customers and mechanical sympathy are performance efficiency principles.
- Measuring business outcomes against costs and granular cost allocation are cost optimization principles.
- Maximizing utilization and minimizing the footprint of data processing are sustainability principles.
Trap: Cost optimization focuses on the price of delivering business value. Sustainability focuses on reducing energy consumption and the resources needed.
From the AWS docs (11)
- Operational excellence is the ability to support development and run workloads effectively, gain insight into their operations, and continuously improve processes and procedures to deliver business value.
- Performance efficiency is the ability to use computing resources efficiently to meet system requirements and to keep that efficiency as demand changes and technologies evolve.
- Cost optimization is the ability to run systems that deliver business value at the lowest price point.
- Sustainability is the ability to continually improve sustainability impacts by reducing energy consumption and increasing efficiency, getting the most from provisioned resources and minimizing the total resources required.
- A production-scale test environment can be created on demand and decommissioned after testing, so you pay for it only while it runs.
- An operational excellence design principle is safely automate where possible: define the whole workload and its operations as code and run procedures automatically.
- Security pillar design principles: implement a strong identity foundation, maintain traceability, apply security at all layers, automate security best practices, protect data in transit and at rest, keep people away from data, and prepare for security events.
- Operational excellence design principles: implement observability for actionable insights, safely automate where possible, make frequent small reversible changes, refine operations frequently, anticipate failure, learn from all operational events and metrics, and use managed services.
- Performance efficiency design principles: use managed services to reduce operational complexity, deploy workloads closer to your customers, build scalable architectures, experiment more often, consider mechanical sympathy, and design for change and variable demand.
- Cost optimization design principles: implement Cloud Financial Management, adopt a consumption model, measure business outcomes relative to costs, use managed services and automation, and implement granular cost allocation.
- Sustainability design principles: understand your impact, establish sustainability goals, maximize utilization, anticipate and adopt more efficient hardware and software, align the computational approach to problem complexity, and minimize the footprint of data and its processing.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 26 cards as a list
What are the six pillars of the AWS Well-Architected Framework?
Operational excellence, security, reliability, performance efficiency, cost optimization and sustainability.
A workload must perform its intended function correctly and consistently, and recover from failures. Which AWS Well-Architected pillar covers this?
Reliability.
A company wants to protect data, systems and assets using cloud technologies. Which AWS Well-Architected pillar covers this?
Security.
Which AWS Well-Architected general design principle says to simulate production events regularly to find weaknesses?
Improve through game days.
Is cost optimization in the AWS Well-Architected Framework about spending as little as possible?
No. It means delivering business value at the lowest price point; the cheapest option can fail other pillars such as reliability.
A monolithic application fails completely when one component fails. Which Well-Architected recommendation addresses this?
Loosely coupled dependencies (reliability pillar), for example with Amazon SQS queues between components.
A company runs its Amazon RDS database in multiple Availability Zones so it fails over automatically. Which Well-Architected pillar does this serve?
Reliability: automatically recover from failure and remove single points of failure.
What is the AWS Well-Architected Framework used for?
It provides best practices and questions for evaluating how well an architecture aligns with AWS guidance.
Which AWS Well-Architected pillar focuses on a workload performing its intended function consistently?
The reliability pillar focuses on a workload performing its intended function correctly and consistently when expected.
Which AWS Well-Architected pillar recommends scaling horizontally to improve workload availability?
The reliability pillar recommends horizontal scaling to increase availability.
Which AWS service reviews a workload against the AWS Well-Architected Framework and produces an improvement plan?
The AWS Well-Architected Tool. It guides a self-review, lists high and medium risk issues, and builds an improvement plan.
A company wants to document the architecture decisions for a workload and get improvement recommendations based on AWS best practices. Which AWS service fits?
The AWS Well-Architected Tool. It documents decisions and recommends improvements based on the Well-Architected Framework.
Besides reviewing a single workload, what can an organization use the AWS Well-Architected Tool for?
Documenting its architectures, governing product launches, and understanding and managing the risks across its technology portfolio.
Does the AWS Well-Architected Tool change a workload's resources to fix the risks it finds?
No. It is a guided self-review that documents risks and an improvement plan; you make the changes.
Who carries out a review in the AWS Well-Architected Tool?
The customer's own team. The tool guides a self-review and produces the risks and an improvement plan.
A team wants to run its workload effectively, learn from operations and keep improving its procedures. Which AWS Well-Architected pillar covers this?
Operational excellence.
A company wants to keep using compute resources efficiently as demand changes and new instance types appear. Which AWS Well-Architected pillar covers this?
Performance efficiency.
A company wants to deliver business value at the lowest price point. Which AWS Well-Architected pillar covers this?
Cost optimization.
A company wants to reduce the energy its workload consumes and the total resources it needs. Which AWS Well-Architected pillar covers this?
Sustainability.
How does the AWS Cloud make testing at production scale affordable, according to the Well-Architected Framework?
Create the production-scale environment on demand, test, then decommission it. You pay only while it runs.
Which Well-Architected pillar includes the design principle of defining the workload and its operations as code?
Operational excellence (safely automate where possible).
Which Well-Architected pillar has the design principles "maintain traceability" and "keep people away from data"?
Security.
"Make frequent, small, reversible changes" and "anticipate failure" are design principles of which Well-Architected pillar?
Operational excellence.
"Deploy workloads closer to your customers" and "consider mechanical sympathy" are design principles of which Well-Architected pillar?
Performance efficiency.
"Measure business outcomes relative to costs" and "implement granular cost allocation" are design principles of which Well-Architected pillar?
Cost optimization.
"Maximize utilization" and "minimize the footprint of data and its processing" are design principles of which Well-Architected pillar?
Sustainability.