Cloud Architecture Guide
DAY_02 / SECTION_01 // PATTERNS
MODULE READY

AWS Well-Architected Framework

A vendor-published, freely-available set of design principles you can use on any cloud — not just AWS. Six pillars, each with concrete questions to ask of an architecture. Same ideas appear in Azure WAF and GCP Architecture Framework under different names.

PILLAR_01
ONLINE
settings_suggest

Operational Excellence

Run + improve
Run and monitor systems, gain insight, continuously improve. Operations as code, small reversible changes, learn from every event.
PILLAR_02
ONLINE
shield

Security

Protect
Strong identity foundation · enable traceability · security at all layers · automate · protect data in transit and at rest · keep people away from data.
PILLAR_03
ONLINE
health_and_safety

Reliability

Stay up
Recover automatically · test recovery · scale horizontally · stop guessing capacity · manage change in automation.
PILLAR_04
IDLE
speed

Performance Efficiency

Use what's needed
Democratize advanced tech · go global in minutes · use serverless · experiment more often · pick the right tool for the workload.
PILLAR_05
IDLE
payments

Cost Optimization

FinOps
Cloud Financial Management · consumption model · measure efficiency · stop paying for undifferentiated heavy lifting · attribute spend.
PILLAR_06
STANDBY
eco

Sustainability

Footprint
Understand your impact · sustainability goals · maximize utilization · use managed services · reduce downstream impact. (Added 2021.)
// how to use the framework in practice

Read the framework's questions, not just the principles. AWS publishes ~50 questions across the six pillars — each is a tractable conversation you can have with a team. "How do you mitigate deployment risks?" is more useful than "be operationally excellent."

// links: aws.amazon.com/architecture/well-architected · learn.microsoft.com/azure/well-architected · cloud.google.com/architecture/framework

help Knowledge Check
Question 1/1

Your team is debating whether to use a managed Kubernetes service (EKS) or self-host K8s on EC2 to save licensing fees. Which Well-Architected pillar most directly weighs against self-hosting?

// pick one to verify