--- name: aws-waf-reliability metadata: category: WellArchitectedFramework description: >- Generates guidance for reliability, availability, fault isolation and disaster recovery for AWS workloads, based on the Reliability pillar of the AWS Well-Architected Framework. Use when evaluating, designing or improving how an AWS workload withstands and recovers from failure. --- # AWS Well-Architected Framework skill for the Reliability pillar ## Overview The Reliability pillar is the ability of a workload to perform its intended function correctly and consistently when it is expected to. AWS organizes it into foundations, workload architecture, change management and failure management. ## Core principles The recommendations below follow the published framework. Written for this agent from AWS's published Well-Architected Framework. Question codes are AWS's. - **Automatically recover from failure**: Monitor key indicators, and trigger recovery when a threshold is crossed. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/rel-dp.html - **Test recovery procedures**: Simulate failures to prove recovery works. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/rel-dp.html - **Scale horizontally to increase aggregate workload availability**: Replace one large resource with many small ones. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/rel-dp.html - **Stop guessing capacity**: Monitor demand, and add or remove resources automatically. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/rel-dp.html - **Manage change through automation**: Make and track changes to infrastructure by automation. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/rel-dp.html ## Relevant products The following are _examples_ of products relevant to this pillar: - **Compute**: Multiple Availability Zones, Amazon EC2 Auto Scaling, Amazon ECS, Amazon EKS, AWS Lambda - **Networking**: Elastic Load Balancing, Amazon Route 53, AWS Global Accelerator - **Data**: Amazon RDS Multi-AZ, Amazon Aurora Global Database, Amazon S3 replication, DynamoDB global tables - **Recovery and testing**: AWS Backup, AWS Elastic Disaster Recovery, AWS Fault Injection Service, Service Quotas ## Workload assessment questions Ask appropriate questions to understand the requirements and constraints of the workload and the organization. Choose from this list: - REL 1: How do you manage Service Quotas and constraints? - REL 2: How do you plan your network topology? - REL 3: How do you design your workload service architecture? - REL 4: How do you design interactions in a distributed system to prevent failures? - REL 5: How do you design interactions in a distributed system to mitigate or withstand failures? - REL 6: How do you monitor workload resources? - REL 7: How do you design your workload to adapt to changes in demand? - REL 8: How do you implement change? - REL 9: How do you back up data? - REL 10: How do you use fault isolation to protect your workload? - REL 11: How do you design your workload to withstand component failures? - REL 12: How do you test reliability? - REL 13: How do you plan for disaster recovery (DR)? ## Validation checklist Use this checklist to evaluate the architecture against this pillar: - Service quotas are known and monitored. - The network has room to grow and no address overlap. - Components are loosely coupled. - Timeouts, retries with backoff, and throttling are designed in. - The workload runs across multiple Availability Zones. - Scaling is automatic and tested. - Backups are automated, and restores are tested. - The DR strategy meets stated RTO and RPO, and is rehearsed. - Failure injection is part of testing.