All guides
Practice now
D4 · Migration and Modernization

Well-Architected Framework — the 6 pillars in depth

The is AWS's reference framework for evaluating and improving architectures. For the SAP-C02, you need to know not just the names of the pillars, but how they're concretely implemented with AWS services and how the Well-Architected Review process is applied.

Icon-Architecture/48/Arch_AWS-Organizations_48

The 6 pillars of the Well-Architected Framework

⚙️

Operational Excellence

Run and monitor systems to deliver business value and continuously improve processes and procedures.

🔒

Security

Protect information, systems and assets while delivering business value through risk assessment and mitigation.

🛡️

Reliability

The ability of a workload to perform its intended function correctly and consistently when expected.

⚡

Performance Efficiency

Use IT and computing resources efficiently to meet system requirements and maintain efficiency as demand changes.

💰

Cost Optimization

Avoid unnecessary costs. Understand and control spending, select the right type and number of resources.

🌱

Sustainability

Minimize the environmental impact of cloud workloads. The 6th pillar, added in 2021.

Icon-Architecture/48/Arch_AWS-CloudFormation_48

Pillar 1: Operational Excellence

Design principles

  • Perform operations as code: infrastructure as code (, CDK), automated runbooks
  • Make frequent, small, reversible changes: small, frequent deployments with rollback capability
  • Refine operations procedures frequently: review runbooks after every incident, update them regularly
  • Anticipate failure: run pre-mortems, chaos testing, game days
  • Learn from all operational failures: blameless post-mortems, share learnings across teams

Key AWS services

AWS CloudFormation/CDKInfrastructure as code — repeatable, auditable operations
AWS Systems ManagerAutomated runbooks, patch management, Session Manager
Amazon CloudWatchMetrics, logs, alarms, dashboards for operational visibility
AWS X-RayDistributed tracing for debugging complex systems
AWS DevOps GuruML that detects operational anomalies before they impact users
AWS CodePipeline/CodeDeployCI/CD with automated blue/green and canary deployments
Icon-Architecture/48/Arch_AWS-Shield_48

Pillar 2: Security

7 best practices of the security pillar

  • Implement a strong identity foundation: IAM Identity Center, least privilege, eliminate long-lived credentials
  • Enable traceability: , , for every change
  • Apply security at all layers: SGs, NACLs, WAF, Network Firewall, encryption
  • Automate security best practices: AWS Config auto-remediation, Security Hub
  • Protect data in transit and at rest: mandatory TLS, for encryption at rest
  • Keep people away from data: no direct human access to production data (SSM Session Manager, not SSH)
  • Prepare for security events: playbooks, documented incident response plan

Key AWS services for the pillar

  • IAM Identity Center (unified SSO)
  • AWS CloudTrail (API auditing)
  • AWS Config (configuration compliance)
  • Amazon GuardDuty (threat detection)
  • AWS Security Hub (centralized posture)
  • AWS KMS / CloudHSM (key management)
  • Amazon Inspector (vulnerabilities)
  • AWS Certificate Manager (TLS)
  • Icon-Architecture/48/Arch_AWS-Backup_48

    Pillar 3: Reliability

    5 reliability design principles

    • Automatically recover from failure: health checks + ASG automatically replace failed instances
    • Test recovery procedures: run real failovers (game days, AWS FIS)
    • Scale horizontally: multiple small instances > one large one. Eliminates SPOFs
    • Stop guessing capacity: Auto Scaling reacts to real demand without over/under provisioning
    • Manage change through automation: CloudFormation for predictable, reversible changes

    Key AWS services for the pillar

  • Amazon Route 53 (DNS failover)
  • AWS Auto Scaling (automatic scaling)
  • Elastic Load Balancing (traffic distribution)
  • Amazon RDS Multi-AZ (database HA)
  • AWS Backup (managed backups)
  • AWS Resilience Hub (resilience scoring)
  • (alarms and health checks)
  • AWS Fault Injection Service (chaos testing)
  • Icon-Architecture/48/Arch_AWS-Compute-Optimizer_48

    Pillar 4: Performance Efficiency

    Design principles

    • Democratize advanced technologies: use managed services instead of running your own technology (SageMaker vs your own ML server)
    • Go global in minutes: deploy across multiple regions to reduce global latency
    • Use serverless architectures: Lambda, Fargate remove the overhead of managing servers
    • Experiment more often: easily try alternative instance types or configurations
    • Consider mechanical sympathy: use the right service for the use case

    Performance decisions

    ComputeEC2 (control), Lambda (scale to 0), Fargate (serverless containers), Graviton (price/performance)
    StorageEBS io2 (IOPS), EFS (shared), FSx Lustre (HPC), S3 (objects)
    DatabaseRDS (relational), DynamoDB (key-value at scale), ElastiCache (cache), Redshift (OLAP)
    NetworkCloudFront (CDN), Global Accelerator (routing), Enhanced Networking (HPC)
    Icon-Architecture/48/Arch_AWS-Cost-Explorer_48

    Pillar 5: Cost Optimization

    5 design principles

    • Implement cloud financial management: build a FinOps team, cost allocation tags
    • Adopt a consumption model: pay for what you use, scale to zero when there's no demand
    • Measure overall efficiency: business value delivered vs cost incurred
    • Stop spending on undifferentiated heavy lifting: use managed services instead of managing DBs, OS, etc.
    • Analyze and attribute expenditure: granular tagging for visibility by project/team

    Key AWS services

  • AWS Cost Explorer (analysis and forecasts)
  • AWS Budgets (budget alerts)
  • AWS Compute Optimizer (rightsizing)
  • Cost Anomaly Detection (ML detection)
  • Savings Plans / Reserved Instances
  • Spot Instances (up to 90% discount)
  • S3 Intelligent-Tiering (automatic lifecycle)
  • Trusted Advisor (cost recommendations)
  • Icon-Architecture/48/Arch_Amazon-EC2_48

    Pillar 6: Sustainability (the 6th pillar)

    Added in 2021. Focused on minimizing the environmental impact of cloud workloads. For the SAP-C02 it's not as frequent as the other 5, but it can appear in questions about responsible cloud practices.

    Design principles

    • Understand your impact: measure carbon footprint with the AWS Customer Carbon Footprint Tool
    • Establish sustainability goals: efficiency metrics per unit of business value
    • Maximize utilization: higher instance utilization = fewer resources = less energy
    • Adopt more efficient hardware: Graviton is more energy-efficient than x86
    • Use managed services: AWS optimizes the efficiency of shared hardware
    • Reduce downstream impact: more efficient apps = less compute on edge and client devices

    Sustainability practices on AWS

    • Graviton3: up to 60% less energy than equivalent x86 instances
    • AWS Graviton on Fargate: more efficient container workloads
    • S3 Intelligent-Tiering: reduces active storage of rarely accessed data
    • Lambda + auto-scaling: eliminates idle instances during periods without traffic
    • AWS Customer Carbon Footprint Tool: reports carbon emissions from your AWS usage
    Icon-Architecture/48/Arch_AWS-Organizations_48

    Well-Architected Review (WAR) — evaluation process

    The WAR is a structured conversation about the architecture based on ~300 questions organized across the 6 pillars. The result is a report with High Risk Issues (HRIs) and Medium Risk Issues (MRIs) with concrete recommendations.

    1.

    Define the workload

    Identify the system under review, its boundaries, stakeholders, and where it is in its lifecycle.

    2.

    Answer the WAR Tool questions

    For each pillar, answer whether each best practice applies. Document decisions and trade-offs made consciously.

    3.

    Review findings

    Identify High Risk Issues (HRIs): critical failure, security gap, extreme cost. Medium Risk Issues (MRIs): areas for improvement.

    4.

    Prioritize improvements

    Not all HRIs are equal — prioritize by business impact, likelihood of occurrence, and remediation effort.

    5.

    Implement and re-review

    The WAR is iterative — re-evaluate periodically (at least once a year or after major changes).

    AWS Well-Architected Tool

    Free service in the AWS console. Guides the WAR process, generates the report automatically, integrates with AWS Trusted Advisor and can be shared with AWS Partners.

    Custom Lenses

    Extends the WAR Tool with questions specific to your industry (finance, healthcare, government) or compliance requirements. Shareable across the organization.

    Icon-Architecture/48/Arch_AWS-Organizations_48

    Common exam traps

    Trap: "The Well-Architected Framework has 5 pillars"

    Reality: Since 2021 there are 6 pillars. The 6th is Sustainability. Exam answers that list only 5 pillars and omit Sustainability will be incorrect.

    Trap: "The WAR is an audit AWS performs on your architecture"

    Reality: The WAR is a structured self-assessment that YOU (or an AWS Partner) perform on your architecture using the AWS Well-Architected Tool. AWS does not proactively audit or evaluate your architecture.

    Trap: "Well-Architected means maximizing every pillar simultaneously"

    Reality: The pillars involve trade-offs with each other. Maximizing security can reduce performance. Maximizing reliability increases cost. The architect decides the right trade-offs for the business requirements — there is no architecture that is perfect across every pillar.

    Did you get this topic?

    Test what you just learned

    An architecture team runs a Well-Architected Review of their e-commerce application. They find they currently have: a single RDS instance without Multi-AZ, CloudTrail disabled in 3 accounts, and they're paying On-Demand for 50 EC2 instances that have been running for 2 years. The CTO asks which High Risk Issue is the most critical to resolve first. What is the correct priority?

    Ready to test "Well-Architected Framework: the 6 pillars in depth"?

    Put what you learned to the test with original SAP-C02 exam questions.

    Start SAP-C02 mock exam

    Unlimited mock exams with the Pro plan

    Log in to track your progress.