Skip to content

AWS Well-Architected Framework

Overview

The AWS Well-Architected Framework helps cloud architects build secure, high-performing, resilient, and efficient infrastructure for applications. It consists of six pillars that provide a consistent approach to evaluating architectures and implementing designs that scale over time.


Six pillars at a glance

flowchart TB
  WAF[AWS Well-Architected<br/>Framework]
  WAF --> P1[Operational<br/>Excellence<br/>run + improve]
  WAF --> P2[Security<br/>protect data +<br/>systems + identity]
  WAF --> P3[Reliability<br/>recover from failure<br/>scale to demand]
  WAF --> P4[Performance<br/>Efficiency<br/>use compute right]
  WAF --> P5[Cost<br/>Optimization<br/>spend mindfully]
  WAF --> P6[Sustainability<br/>environmental<br/>impact]

  WAF -. evaluated via .-> WATool[Well-Architected Tool<br/>workload review]
  WAF -. extended by .-> Lenses[Lenses:<br/>Serverless, SaaS,<br/>ML, Data Analytics,<br/>FTR, IoT, Healthcare,<br/>Financial Services,<br/>GenAI]

Each pillar has design principles + best practices. The Well-Architected Tool (free in the AWS console) walks a workload through each pillar's questions and surfaces high/medium-risk gaps. Lenses adapt the framework for specialized domains (ML, SaaS, GenAI, etc.).


The Six Pillars

1. Operational Excellence

Principle Description Key Services
Perform operations as code Use IaC for all infrastructure CloudFormation, CDK, Terraform
Make frequent, small, reversible changes Small deployments with rollback CodeDeploy, feature flags
Refine operations procedures frequently Regular runbook reviews Systems Manager, runbooks
Anticipate failure Pre-mortem analysis, chaos engineering FIS, game days
Learn from operational failures Post-incident reviews CloudWatch, X-Ray, post-mortems

Key Design Principles: - Organization: Evaluate internal/external customer needs, create shared understanding - Prepare: Use IaC, implement observability, mitigate deployment risks - Operate: Define metrics, use runbooks, define escalation paths - Evolve: Implement feedback loops, perform operations improvements

2. Security

Principle Description Key Services
Implement a strong identity foundation Least privilege, centralized identity IAM, Identity Center, Organizations
Maintain traceability Monitor, audit, log all actions CloudTrail, Config, Security Hub
Apply security at all layers Edge, VPC, subnet, instance, OS, application WAF, Security Groups, NACLs
Automate security best practices Automated remediation Config Rules, EventBridge, Lambda
Protect data in transit and at rest Encryption everywhere KMS, ACM, S3 encryption
Keep people away from data Minimize direct data access Athena, automated pipelines
Prepare for security events Incident response plans GuardDuty, Detective, Macie

3. Reliability

Principle Description Key Services
Automatically recover from failure Self-healing architectures Auto Scaling, Route 53 health checks
Test recovery procedures Validate DR regularly FIS, backup restore testing
Scale horizontally Distribute load across resources ALB, Auto Scaling, DynamoDB
Stop guessing capacity Use auto-scaling Auto Scaling, Lambda, Fargate
Manage change through automation IaC for all changes CloudFormation, CodePipeline

Key Reliability Concepts: - Foundations: Service quotas, network topology - Workload Architecture: Distributed system design, fault isolation - Change Management: Monitoring, auto-scaling, change automation - Failure Management: Backup, DR, fault isolation boundaries

4. Performance Efficiency

Principle Description Key Services
Democratize advanced technologies Use managed services Aurora, Kinesis, SageMaker
Go global in minutes Deploy globally with ease CloudFront, Global Accelerator, multi-region
Use serverless architectures Remove server management overhead Lambda, Fargate, DynamoDB
Experiment more often A/B testing, benchmarking CloudWatch, performance testing
Consider mechanical sympathy Use the right tool for the job Instance families, storage types

5. Cost Optimization

Principle Description Key Services
Implement cloud financial management FinOps practices Cost Explorer, Budgets, CUR
Adopt a consumption model Pay only for what you use Lambda, Fargate, on-demand
Measure overall efficiency Track cost per business outcome Custom metrics, CUR analysis
Stop spending on undifferentiated heavy lifting Use managed services RDS, ECS, S3
Analyze and attribute expenditure Tag and track costs Cost allocation tags, Organizations

6. Sustainability

Principle Description Key Services
Understand your impact Measure carbon footprint Customer Carbon Footprint Tool
Establish sustainability goals Set targets for efficiency CloudWatch custom metrics
Maximize utilization Right-size and scale Compute Optimizer, auto-scaling
Anticipate and adopt new offerings Use efficient services Graviton instances, serverless
Reduce downstream impact Minimize data transfer CloudFront caching, compression

Well-Architected Tool

Feature Description
Workload Review Answer questions per pillar for each workload
Lens Apply specific lenses (Serverless, SaaS, ML, etc.)
Milestones Track improvements over time
Dashboard View risks across workloads
Integration Generate improvement plans

Well-Architected Lenses

Lens Focus Area
Serverless Applications Lambda, API Gateway, Step Functions
SaaS Multi-tenancy, isolation, onboarding
Machine Learning ML lifecycle, model training, inference
Data Analytics Data lakes, ETL, analytics
IoT Device management, data ingestion
Financial Services Regulatory compliance, resilience
Games Industry Real-time, global scale
SAP SAP on AWS architecture

Common Anti-Patterns

Anti-Pattern Pillar Solution
No IaC Operational Excellence Adopt CloudFormation/CDK/Terraform
Over-permissive IAM Security Implement least privilege with Access Analyzer
Single-AZ deployment Reliability Deploy across multiple AZs
Over-provisioned instances Cost Optimization Right-size with Compute Optimizer
No monitoring All pillars Implement CloudWatch, X-Ray, alarms
Manual deployments Operational Excellence CI/CD with CodePipeline

Certification Exam Relevance

The Well-Architected Framework is fundamental to: - AWS Solutions Architect Associate (SAA-C03) - AWS Solutions Architect Professional (SAP-C02) - AWS DevOps Professional (DOP-C02) - AWS SysOps Administrator (SOA-C02)


  • AWS Well-Architected Framework: https://docs.aws.amazon.com/wellarchitected/latest/framework/
  • Well-Architected Tool: https://docs.aws.amazon.com/wellarchitected/latest/userguide/
  • Well-Architected Labs: https://wellarchitectedlabs.com/
  • Well-Architected Lenses: https://docs.aws.amazon.com/wellarchitected/latest/userguide/lenses.html