Help Center/ Well-Architected Framework/ Well-Architected Framework and Practices/ Resilience Pillar/ Rapid Fault Recovery/ RES10 Fault Isolation/ RES10-04 Configuring Health Check and Automatic Isolation
Updated on 2025-05-22 GMT+08:00
View PDF
Share

RES10-04 Configuring Health Check and Automatic Isolation

If an unhealthy component is detected, it is automatically isolated to minimize the impact scope.

  • Risk level

    High

  • Key strategies
    • Perform health check periodically on system components to check whether they are normal.
    • Ensure abnormal components can be automatically isolated to prevent impacts on services.
  • Related cloud services and tools
    • Elastic Load Balance (ELB): supports health check. ELB periodically sends requests to backend servers to detect their statuses and check whether they can process requests. If an unhealthy backend server is detected, the load balancer will stop routing requests to it.
    • Cloud Container Engine (CCE): supports container health check. When containers are running, CCE periodically checks the container health based on user requirements. If health check is not configured, application exceptions cannot be detected, and the pod cannot automatically restart to recover the application. As a result, the pod is normal, but the application is abnormal.
Parent topic: RES10 Fault Isolation