Build it right: six pillars

Best practices, written down

The AWS Well-Architected Framework is AWS's collection of design principles, best practices and review questions for building and running workloads in the cloud. It is organized into six pillars. Teams use the free AWS Well-Architected Tool in the console to answer the questions for one workload and get a list of risks to fix. It's a review guide, not a service that changes anything for you.

Exam tip Trap: the Well-Architected Tool reviews a design and reports risks. It doesn't scan resources or fix them; that's Trusted Advisor and other services.

Operational excellence: run it and improve it

Operational excellence is about running and monitoring systems to deliver business value, and improving the processes that support them. Its design principles include: safely automate where possible (operations as code), make frequent small reversible changes, refine procedures often, anticipate failure, and learn from every operational event.

Dev: Small changes you can undo beat one giant Friday-night change you can't.

Security: protect data, systems and assets

The security pillar covers protecting information and systems. Principles: build a strong identity foundation (least privilege), turn on traceability (log and monitor who did what), apply security at all layers, automate security best practices, protect data in transit and at rest, keep people away from data where possible, and prepare for security events.

Priya: Every one of those becomes a chapter later. Remember "identity first, then logs".

Reliability: work correctly, recover quickly

Reliability is a workload's ability to perform its intended function correctly and consistently, and to recover from failures. Principles: automatically recover from failure, test recovery procedures, scale horizontally (many small resources instead of one big one, so one failure hurts less), stop guessing capacity, and manage change through automation.

Exam tip Words that point to reliability: recover, failover, withstand a failure, backups tested, multiple Availability Zones.

Performance efficiency: the right resource for the job

Performance efficiency means using computing resources efficiently to meet requirements, and staying efficient as demand and technology change. Principles: use advanced technologies as managed services, go global in minutes, use serverless architectures, experiment more often, and pick the tool that fits the job (AWS calls it "mechanical sympathy").

Ranger: chooses the softest dog bed in the room Woof.

You: Right resource for the job. He gets it.

Cost optimization: value at the lowest price

Cost optimization is running systems that deliver business value at the lowest price point. Principles: practice cloud financial management, adopt a consumption model (pay only for what you use), measure overall efficiency, stop spending money on undifferentiated heavy lifting (let AWS run data centers), and analyze and attribute spending so each team sees its bill.

Sustainability: less impact on the planet

Sustainability, the newest pillar, is about reducing the environmental impact of running cloud workloads. Principles: understand your impact, set goals, maximize utilization (no idle servers burning power), adopt newer more efficient hardware and software, use managed services, and reduce the energy needed by your users' devices and downstream systems.

Exam tip Cost and sustainability often agree (turning off idle servers helps both). Pick sustainability when the question talks about energy, carbon or environmental goals.

Pairs that look alike

Ask "what is this practice protecting against?" and the pillar usually jumps out.

• Reliability vs performance efficiency: surviving and recovering from failure vs using the right, efficient resources for the load
• Cost optimization vs sustainability: money vs environmental impact, even when one action helps both
• Operational excellence vs reliability: how you run, monitor and improve operations vs how the workload withstands failure
• Security vs operational excellence: protecting data and access vs running changes and procedures well

Exam tip If two pillars both fit, choose the one the question's goal names: "recover", "faster", "cheaper", "greener", "auditable", "fewer manual steps".

Why AWS cares about all six

The pillars trade off. Running the shop in three Availability Zones raises reliability but costs more. Rightsizing cuts cost but could hurt performance if you shrink too far. A Well-Architected review makes these trade-offs on purpose instead of by accident, and you repeat it as the business changes.

Dev: Nobody aces all six on day one. We review, fix the high risks, and review again next quarter.