Introduction to the Well-Architected Framework

The AWS Well-Architected Framework provides a consistent approach for customers and partners to evaluate architectures and implement designs that will scale over time. It was created by AWS Solutions Architects based on years of experience reviewing thousands of customer workloads across every industry.

---

Why the Framework Exists

Building on the cloud is different from building in a traditional data centre. Without guardrails, teams can easily create architectures that are insecure, unreliable, inefficient, or unnecessarily expensive. The Well-Architected Framework exists to prevent these pitfalls by codifying best practices into a structured review process.

Before the framework, architectural decisions were often:

• Ad hoc — made by individual engineers without a shared standard
• Inconsistent — varying widely between teams within the same organisation
• Reactive — problems were discovered in production rather than during design
• Undocumented — decisions lacked traceability, making audits difficult

The framework addresses all of these issues by providing a common language and a repeatable evaluation methodology.

---

The Six Pillars

The framework is organised around six pillars, each representing a fundamental area of cloud architecture:

Pillar	Focus
Operational Excellence	Running and monitoring systems to deliver business value and continually improve processes
Security	Protecting information, systems, and assets while delivering business value through risk assessment and mitigation
Reliability	Ensuring a workload performs its intended function correctly and consistently
Performance Efficiency	Using computing resources efficiently to meet system requirements and maintaining efficiency as demand changes
Cost Optimisation	Running systems to deliver business value at the lowest price point
Sustainability	Minimising the environmental impact of running cloud workloads

Each pillar contains a set of design principles and best practices. No single pillar is more important than another — a well-architected workload balances all six.

---

Design Principles

The framework promotes several overarching design principles that apply across all pillars:

Stop Guessing Your Capacity Needs

In the cloud, you can scale up or down based on actual demand rather than forecasting months in advance. This eliminates the risk of over-provisioning (wasted money) or under-provisioning (poor performance).

Test Systems at Production Scale

You can create a full-scale test environment on demand, run your tests, and then tear it down. This means you can validate your architecture under realistic conditions without maintaining expensive test infrastructure permanently.

Automate to Make Architectural Experimentation Easier

Automation lets you create and replicate workloads at low cost. You can track changes, audit the impact, and revert when necessary. Infrastructure as code makes your architecture versionable and repeatable.

Allow for Evolutionary Architectures

In a traditional environment, architectural decisions are often treated as fixed, one-time choices. In the cloud, the ability to automate and test on demand lowers the risk of change, allowing systems to evolve over time as your business needs grow.

Drive Architectures Using Data

In the cloud, you can collect data on how your architecture affects the behaviour of your workload. This lets you make fact-based decisions about how and when to improve your architecture.

Improve Through Game Days

Simulate events in production to test your architecture and your team's response. Game days help you understand where improvements can be made and build confidence in your processes.

---

How the Framework Is Used

The Well-Architected Framework is not a one-time checklist. It is designed to be used throughout the lifecycle of a workload:

1. During design — use the pillars and design principles to guide architectural decisions
2. Before launch — conduct a Well-Architected Review to identify risks
3. After launch — periodically review your workload to ensure it remains aligned with best practices as AWS services evolve
4. During incidents — refer to the framework to understand whether an issue stems from an architectural gap

AWS provides the AWS Well-Architected Tool in the console, which guides you through structured review questions for each pillar. We will cover this tool in detail in a later lesson.

---

Well-Architected Lenses

In addition to the general framework, AWS offers lenses that provide additional guidance for specific industry or technology domains. Examples include:

• Serverless Lens — best practices for serverless architectures
• SaaS Lens — guidance for multi-tenant SaaS applications
• Data Analytics Lens — optimising data pipelines and analytics workloads
• Machine Learning Lens — building reliable and efficient ML systems
• Financial Services Lens — meeting regulatory requirements in financial services
• IoT Lens — designing scalable and secure IoT solutions

Lenses extend the base framework without replacing it. You apply a lens alongside the six pillars to get domain-specific guidance.

---

The Well-Architected Review Process

A Well-Architected Review is a structured conversation between a solutions architect and the workload team. The process typically follows these steps:

1. Select the workload — choose a specific application or system to review
2. Answer the pillar questions — work through the questions for each pillar, discussing current practices and identifying gaps
3. Identify high-risk issues (HRIs) — flag areas where the architecture deviates significantly from best practices
4. Create an improvement plan — prioritise the HRIs and define actionable steps to remediate them
5. Implement improvements — make the changes and track progress
6. Re-review — periodically repeat the review to ensure continued alignment

The review is collaborative, not adversarial. Its purpose is to help teams improve, not to assign blame.

---

Who Should Use the Framework?

The framework is valuable for anyone involved in building or operating cloud workloads:

• Architects — to design robust, scalable systems
• Developers — to understand the operational and security implications of their code
• DevOps engineers — to build automated, observable, and resilient pipelines
• Managers — to understand the trade-offs and risks in their team's architecture
• Compliance teams — to verify that workloads meet regulatory and organisational standards

---

Summary

The AWS Well-Architected Framework provides a structured, repeatable methodology for evaluating and improving cloud architectures. It is built on six pillars — Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimisation, and Sustainability — each offering design principles and best practices. The framework is used throughout the lifecycle of a workload and can be extended with domain-specific lenses.

In the next lesson, we will dive into the first pillar: Operational Excellence.