Cloud concept · Updated

AWS Well-Architected Framework - The AWS Well-Architected Framework is a structured set of architectural principles and review practices for assessing and improving cloud workloads across six quality pillars.

In short

The framework helps engineers evaluate operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability through documented questions and best practices. For security governance, it connects architectural decisions to risk reduction and improvement plans, but it does not replace automated resource checks, compliance evidence, or regulatory audits.

Cloud Concepts Hub →

7 key aspects of AWS Well-Architected Framework

The framework combines six architectural pillars with repeatable workload reviews to identify risks, explain trade-offs, and track practical improvements.

01
Operational excellence

Operate workloads through defined ownership, observable behavior, repeatable procedures, and continuous improvement. Use version-controlled infrastructure and tested runbooks so changes and incident responses do not depend on undocumented individual knowledge.

02
Security

Protect systems and data through identity controls, traceability, defense in depth, automation, data protection, and incident preparation. Evaluate both technical controls and the processes that keep those controls effective, including access reviews and exception handling.

03
Reliability

Design workloads to perform their intended functions consistently and recover from failures. Validate availability and recovery requirements through fault isolation, resilient dependencies, backups, and tested restoration procedures.

04
Performance efficiency

Select and evolve computing resources to meet workload requirements efficiently. Use measurements and representative testing to choose architectures and resource types rather than relying on assumptions or permanent overprovisioning.

05
Cost optimization

Understand expenditure and select resources that deliver required business outcomes at an appropriate cost. Establish ownership, measure usage, and remove waste without undermining required security or reliability controls.

06
Sustainability

Reduce the environmental impact of cloud workloads by improving utilization and reducing unnecessary resource demand. Consider data lifecycle, workload scheduling, and architecture choices while preserving business and compliance requirements.

07
Evidence-informed, iterative reviews

Assess a defined workload using consistent questions, document identified risks, and prioritize improvements. Revisit the assessment after material changes and distinguish documented architectural intent from independently verified control implementation.

Cloud services for AWS Well-Architected Framework

AWS Well-Architected Tool provides the structured architectural review and improvement record. AWS Config supplies configuration history and rule evaluations, while AWS Security Hub CSPM supplies security-control results and consolidated findings. AWS CloudTrail provides activity records that support traceability and investigation. AWS Audit Manager can organize relevant evidence for audit assessments. Together, these services connect architectural intent with observable implementation and governance records. Engineers must still define workload scope, interpret findings, document exceptions, and verify that controls satisfy applicable requirements; no single service establishes complete compliance.

AWS Well-Architected ToolAWS Well-Architected Tool

Organizes workload assessments using framework questions and available lenses, records answers, and identifies architectural risks from the review. Milestones help teams compare review states and track improvements, but the tool does not automatically validate every deployed control.

AWS ConfigAWS Config

Records supported resource configurations and evaluates them against AWS Config rules. Conformance packs group rules and remediation actions to support repeatable assessments, providing technical evidence for review topics without assessing the entire architecture.

AWS CloudTrailAWS CloudTrail

Records AWS account activity to support traceability, investigations, and governance evidence. A review should examine event coverage, log protection, retention, and monitoring; data-event logging must be configured where required.

AWS Audit ManagerAWS Audit Manager

AWS Audit Manager has been in maintenance since March 31, 2026, and is closed to new customers; existing customers can continue using it.

AWS Well-Architected Framework exam questions

Real practice exam questions on AWS Well-Architected Framework, with the correct answer and its explanation. Answer them with every option in the exam simulator.

CLF-C02

During an AWS Well-Architected review, a company identifies three findings: unused development resources, an untested recovery procedure for customer payment data, and manual deployment steps for an internal dashboard. The company can fund only one improvement this month. How should the team decide which finding to address first?

Show answerCORRECT ANSWER

Assess each finding's likelihood and business impact against workload requirements, then prioritize the most significant risk.

Architecture reviews support risk-based improvement decisions. The team should evaluate the findings against business requirements, such as acceptable data loss and downtime, rather than assume all findings are equally important.

AIP-C01

A company uses a shared AWS CloudFormation template to deploy Amazon Bedrock retrieval-augmented generation (RAG) applications for several business units. Each deployment has its own source documents, ingestion pipeline, and vector index. During an architectural review, engineers identify a failure scenario: an incorrect document transformation can corrupt retrieved content even though infrastructure health checks remain successful.

Each workload must be able to restore its most recent approved knowledge corpus within 60 minutes after detecting this failure. The platform team must provide a reusable recovery design, and workload owners must demonstrate that it meets the recovery objective at their deployment's data volume.

Which approach best addresses the architectural risk?

Show answerCORRECT ANSWER

Provide reusable backup and recovery automation that preserves approved source-document versions, ingestion configuration, and recoverable vector-index state. Include a runbook for restoring a consistent corpus and switching retrieval to it, and require workload-scale recovery exercises with retrieval validation and measured recovery times.

This design addresses the actual failure boundary: the source data, transformation configuration, and derived retrieval state must be recovered consistently. Reusable automation standardizes implementation, while workload-specific exercises establish whether recovery produces correct results within 60 minutes. This applies the Well-Architected reliability and operational excellence principles rather than treating healthy infrastructure as sufficient evidence of recoverability.

SCS-C03

A healthcare company uses an AWS Systems Manager Automation runbook to contain compromised Amazon EC2 instances. The runbook applies restrictive network controls to the affected instance's entire subnet. Several independent applications share each subnet.

During a security exercise, the runbook successfully contains a simulated compromise but also interrupts an unrelated emergency-care application. A workload architecture review identifies this response design as a business risk. The approved requirements are to block attacker communications from an affected instance within 5 minutes, preserve access for evidence collection, and avoid interrupting unaffected applications. These requirements also apply when the affected instance supports a critical application.

Which improvement to the incident response plan BEST addresses the review finding?

Show answerCORRECT ANSWER

Replace subnet-wide containment with resource-scoped containment procedures that preserve the evidence-collection path. Document decision authority and escalation, and test the revised Automation runbook against both critical and noncritical instances while measuring containment time and unaffected application availability.

This applies risk-informed architectural improvement: reduce the response blast radius while retaining effective containment and investigation capabilities. Documented authority and representative technical exercises demonstrate that the revised procedures meet both security and business requirements, rather than treating successful containment alone as sufficient.

Practice AWS Well-Architected Framework in a full exam

Questions on AWS Well-Architected Framework in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is AWS Well-Architected Framework

2 min read

The AWS Well-Architected Framework provides a repeatable way to examine whether a cloud workload meets its technical and business requirements. Its six pillars are operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. A workload includes the application, infrastructure, data, operational procedures, and people responsible for delivering a business capability. Reviews should therefore cover more than resource configuration: a securely configured application can still have architectural weaknesses if recovery procedures, access ownership, or incident response responsibilities are undefined.

A review begins by defining the workload boundary, business objectives, stakeholders, and relevant requirements. Engineers then answer questions about architectural and operational practices, recording supporting details and identifying gaps. The AWS Well-Architected Tool supports this process by organizing workload reviews, recording answers, identifying risks based on those answers, and tracking improvement progress through milestones. It is not an automatic scanner that independently verifies every resource or certifies the workload as compliant.

For security-focused assessments, important practices include establishing a strong identity foundation, enabling traceability, applying security at multiple layers, automating security practices, protecting data in transit and at rest, limiting direct human access to data, and preparing for security events. For example, a customer-data application might use temporary credentials for operators, separate production from development accounts, encrypt sensitive storage, collect centralized audit logs, and test incident response procedures. The review evaluates whether these controls address the workload's risks and whether the team can demonstrate that they are implemented and maintained.

Architectural review and technical compliance checking are complementary. AWS Config can evaluate recorded resource configurations against rules, while AWS Security Hub CSPM evaluates supported security controls and consolidates findings. These services can reveal implementation gaps, such as overly permissive security groups or missing encryption. A Well-Architected review provides broader context: whether account boundaries are appropriate, whether detection has an accountable owner, and whether exceptions have documented justification. Neither a favorable review nor passing automated checks proves compliance with every legal or contractual obligation.

Consider a payment-processing workload whose review identifies inadequate auditability. The improvement plan might require organization-wide AWS CloudTrail logging, protected log storage, monitored access, and defined retention periods. Engineers can then use configuration checks and collected evidence to verify parts of the implementation. The architectural decision, deployed controls, evidence, and exception process together support governance; recording an affirmative review answer alone does not.

The pillars also expose trade-offs. Additional redundancy can improve availability while increasing cost and resource consumption. Detailed logging improves investigation capability but requires storage planning, access controls, and appropriate handling of sensitive information. Reviews should make these trade-offs explicit rather than maximize one pillar in isolation. Repeat reviews after significant design changes and use milestones to track remediation. High-risk issues are architectural improvement priorities, not necessarily active security incidents, and applying the framework does not require choosing one particular service for every best practice.

Learn AWS Well-Architected Framework in lessons

4 short lessons on AWS Well-Architected Framework in 3 certification courses.

Open the lessons