AWS › Well-Architected Framework

How does the Reliability pillar guide architectural decisions around fault tolerance, disaster recovery, and automatic recovery from failure?

Intermediate

Answer

The Reliability pillar focuses on ensuring a workload performs its intended function correctly and consistently, guiding practices such as automatically recovering from failure by monitoring for signs of trouble and triggering automated responses, scaling horizontally to increase overall system availability, testing recovery procedures regularly rather than assuming they will work when actually needed, and managing change through automation to avoid the human error commonly introduced by manual configuration changes.
// Reliability principle in practice
// Auto Scaling Group automatically replaces unhealthy instances
// Multi-AZ RDS deployment for automatic database failover
Real-world example A company designs its application to automatically detect and replace unhealthy instances through an Auto Scaling Group, and separately conducts quarterly disaster recovery drills to validate that their database failover process actually works as expected under realistic conditions.

Common follow-ups: What is the difference between high availability and disaster recovery in the context of this pillar?;How do you calculate an appropriate recovery time objective for a specific workload?