⭐ Repository → 💼 AWS Well-Architected → 💼 Reliability → 💼 Failure management
💼 Design your workload to withstand component failures
- ID:
/frameworks/aws-well-architected/reliability/failure-management/rel11
Description
Workloads with a requirement for high availability and low mean time to recovery (MTTR) must be architected for resiliency.
Similar
Sub Sections
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| 💼 REL11-BP01 Monitor all components of the workload to detect failures | no data | ||||
| 💼 REL11-BP02 Fail over to healthy resources | no data | ||||
| 💼 REL11-BP03 Automate healing on all layers | no data | ||||
| 💼 REL11-BP04 Rely on the data plane and not the control plane during recovery | no data | ||||
| 💼 REL11-BP05 Use static stability to prevent bimodal behavior | no data | ||||
| 💼 REL11-BP06 Send notifications when events impact availability | no data | ||||
| 💼 REL11-BP07 Architect your product to meet availability targets and uptime service level agreements (SLAs) | no data |