AWS Learning Journey

Is Your Architecture Actually Good? The AWS Well-Architected Framework

The six pillars — operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability — plus the Well-Architected Tool, workload reviews, and how to turn risks into an improvement plan.

8 min read · 1430 words
AWSCloud ArchitectureWell ArchitectedSoftware ArchitectureDevOps
Is Your Architecture Actually Good? The AWS Well-Architected Framework cover image

AWS from Zero to Production — Phase 8, Part 4 of 5 · See the full series roadmap


“Is this a good architecture?”

It’s a hard question to answer without a shared definition of good. One engineer optimizes for cost. Another for latency. A third for security. A fourth just wants fewer pages at night. Reviews turn into opinion contests.

The AWS Well-Architected Framework gives teams that shared definition. It’s built from what AWS has learned from reviewing a very large number of customer architectures, organized into six pillars, each with design principles and specific questions.

It’s not a certification or a checklist to pass. It’s a structured way to find risks — and decide which ones to fix first.

What you’ll walk away with


The six pillars at a glance

Operational excellence   Run and improve the workload effectively
Security                 Protect data, systems, and assets
Reliability              Perform correctly and recover from failure
Performance efficiency   Use resources efficiently as demand changes
Cost optimization        Deliver value at the lowest price point
Sustainability           Minimize environmental impact

You’ve already worked on every one of them in this series. This article connects the dots.


1. Operational excellence

Run the workload well, and keep getting better at it.

Design principles include:

Example question: How do you know your workload is healthy?


2. Security

Protect information, systems, and assets.

Design principles include:

Example question: How do you manage identities for people and machines?


3. Reliability

Perform the intended function correctly and consistently — and recover from failure.

Design principles include:

Example question: How do you back up data? And: How do you test reliability?


4. Performance efficiency

Use computing resources efficiently to meet requirements — as demand and technology change.

Design principles include:

Example question: How do you select the best-performing architecture?


5. Cost optimization

Deliver business value at the lowest price point.

Design principles include:

Example question: How do you decommission resources?


6. Sustainability

Minimize the environmental impact of running workloads.

Design principles include:

Good news: most sustainability improvements are also cost improvements.


The pillars trade off

You can’t maximize everything at once:

Well-Architected doesn’t decide for you. It makes the trade-offs explicit, so the business decides on purpose — not by accident.


The AWS Well-Architected Tool

The AWS Well-Architected Tool is a free service in the AWS console for running reviews:

  1. Define a workload — its name, environment, Regions, and accounts.
  2. Answer the questions for each pillar, choosing which best practices you follow.
  3. Get results — high-risk issues (HRIs) and medium-risk issues (MRIs), with links to guidance.
  4. Save a milestone — a snapshot of the review, so you can track progress over time.
  5. Generate an improvement plan — prioritized actions.

Lenses

Lenses add questions for specific technologies and industries, such as:

You can also create custom lenses with your organization’s own standards — and share them across accounts.


Running a workload review

A practical recipe:

Before

During — about two to four hours

After


Risk identification and remediation

Not every risk is worth fixing right away. For each one, decide:

Typical first-review findings for a workload like the one in this series:

Tip: AWS Trusted Advisor and Security Hub automatically flag many of the same issues, and the Well-Architected Tool can show related Trusted Advisor checks alongside the questions.


Common mistakes


Key takeaways


Quick self-check

Test yourself before moving on:

  1. Name the six pillars.
  2. What does the Well-Architected Tool produce after a review?
  3. What’s a lens?
  4. You found 25 high-risk issues. Do you fix all of them now?

Answers

  1. Operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability.
  2. High- and medium-risk issues, milestones, and an improvement plan.
  3. An additional set of questions for a specific technology, industry, or your own standards.
  4. No. Prioritize by impact and effort; remediate, mitigate, or consciously accept each one.

What’s next

In Part 5, the Phase 8 lab: build a CloudWatch dashboard — as code — for the orders service, with traffic, errors, latency, ECS capacity, load balancer health, application logs, and RDS performance. Then break the database and watch it light up.

Has your team ever run a Well-Architected review? What surprised you? Tell me in the comments.


Share this article

LinkedIn post draft