The AWS Well-Architected Framework
Key Takeaways
- The AWS Well-Architected Framework has six pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability.
- The four SAA-C03 exam domains map directly to four of the six pillars: Security, Reliability, Performance Efficiency, and Cost Optimization.
- The Well-Architected Tool in the AWS Console lets you review workloads against framework best practices for free.
- Design principles include "stop guessing capacity needs," "test systems at production scale," and "automate with architectural experimentation in mind."
- Understanding the pillars and their trade-offs is essential for answering scenario questions where multiple solutions might work.
The AWS Well-Architected Framework
Quick Answer: The AWS Well-Architected Framework has six pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. The four SAA-C03 exam domains map directly to the Security, Reliability, Performance Efficiency, and Cost Optimization pillars.
The AWS Well-Architected Framework is the foundation for everything tested on the SAA-C03. Understanding these pillars helps you think like an AWS architect and select the best answer on scenario questions.
The Six Pillars
| Pillar | Description | SAA-C03 Domain |
|---|---|---|
| Operational Excellence | Run and monitor systems, continuously improve processes | Not directly tested (more SysOps) |
| Security | Protect information, systems, and assets | Domain 1 (30%) |
| Reliability | Recover from failures, meet demand dynamically | Domain 2 (26%) |
| Performance Efficiency | Use resources efficiently as demand changes | Domain 3 (24%) |
| Cost Optimization | Avoid unnecessary costs, optimize spending | Domain 4 (20%) |
| Sustainability | Minimize environmental impact of cloud workloads | Not directly tested |
General Design Principles
The framework outlines key design principles that apply across all pillars:
- Stop guessing your capacity needs — Use Auto Scaling to match demand dynamically
- Test systems at production scale — Create production-scale test environments on demand, then tear them down
- Automate to make architectural experimentation easier — Use CloudFormation, CDK, or Terraform for infrastructure as code
- Allow for evolutionary architectures — Design systems that can evolve as requirements change
- Drive architectures using data — Make decisions based on metrics, not intuition
- Improve through game days — Simulate events in production to test your architecture
Pillar 1: Operational Excellence
Focus: Operations as code, frequent small changes, anticipate failure, learn from all operational events.
Key AWS Services:
- AWS CloudFormation — Infrastructure as code
- AWS Config — Track configuration changes
- Amazon CloudWatch — Monitoring and observability
- AWS Systems Manager — Operational management
- AWS X-Ray — Distributed tracing
Pillar 2: Security
Focus: Protect data, systems, and assets. Implement a strong identity foundation, enable traceability, apply security at all layers, automate security best practices.
Key AWS Services:
- AWS IAM — Identity and access management
- AWS KMS — Key management for encryption
- AWS WAF — Web application firewall
- Amazon GuardDuty — Threat detection
- AWS Shield — DDoS protection
- Amazon Macie — Sensitive data discovery
- AWS CloudTrail — API call logging
Pillar 3: Reliability
Focus: Recover from disruptions, dynamically acquire resources, mitigate failures like misconfigurations and transient network issues.
Key AWS Services:
- Amazon Route 53 — DNS with health checks and failover
- Elastic Load Balancing — Distribute traffic across healthy targets
- Auto Scaling — Automatically adjust capacity
- Amazon S3 — 99.999999999% (11 9s) durability
- Amazon RDS Multi-AZ — Automatic database failover
- AWS Backup — Centralized backup management
Pillar 4: Performance Efficiency
Focus: Use computing resources efficiently to meet requirements and maintain that efficiency as demand changes and technologies evolve.
Key AWS Services:
- Amazon EC2 — Right-sized compute instances
- AWS Lambda — Event-driven serverless compute
- Amazon DynamoDB — Consistent single-digit millisecond performance
- Amazon CloudFront — Global CDN for low-latency delivery
- Amazon ElastiCache — In-memory caching
Pillar 5: Cost Optimization
Focus: Avoid unnecessary costs, understand spending, select the right pricing model, and scale to meet business needs at the lowest cost.
Key AWS Services:
- AWS Cost Explorer — Visualize and manage costs
- AWS Budgets — Set custom cost and usage budgets
- Reserved Instances / Savings Plans — Commit for discounts
- Spot Instances — Use spare capacity at up to 90% discount
- S3 Intelligent-Tiering — Automatic cost optimization for storage
Pillar 6: Sustainability
Focus: Minimize environmental impact by understanding the impact of services, quantifying impact, and reducing it.
Key Concepts:
- Right-size workloads to minimize resource waste
- Use managed services that are more resource-efficient
- Leverage serverless architectures to reduce idle resources
- Choose Regions with lower carbon intensity
The Well-Architected Tool
The AWS Well-Architected Tool is a free service in the AWS Console that helps you review the state of your workloads against architectural best practices. It:
- Provides a consistent approach for evaluating architectures
- Identifies high-risk issues across the six pillars
- Generates a prioritized improvement plan
- Tracks improvements over time
On the Exam: You may see questions about the Well-Architected Tool and when to use it. It is used for architecture reviews, not for compliance auditing (use AWS Config and AWS Audit Manager for that).
How many pillars does the AWS Well-Architected Framework have?
Which Well-Architected Framework pillar maps to the SAA-C03 "Design Resilient Architectures" domain?
Order the SAA-C03 exam domains from highest weight to lowest weight:
Arrange the items in the correct order
Which general design principle suggests creating production-scale test environments on demand?