A company hosts a web application on Amazon EC2 instances inside an Auto Scaling group behind an Application Load Balancer (ALB). The application on one of the EC2 instances becomes unresponsive, causing the ALB target group health check to mark that instance as unhealthy. However, the Auto Scaling group does not terminate or replace the unhealthy instance. Which action will ensure that the Auto Scaling group automatically replaces the unresponsive instance?
- AModify the subnet Network Access Control List (NACL) to allow inbound ephemeral port traffic.
- BUpdate the Application Load Balancer target group health check configuration to query a different port than the application port.
- Change the health check type of the Auto Scaling group from EC2 to ELB.Cevap
- DConfigure an Amazon Route 53 latency routing policy to redirect client traffic away from the unresponsive instance.
Cevap
Change the health check type of the Auto Scaling group from EC2 to ELB.
Changing the health check type of the Auto Scaling group from EC2 to ELB enables the group to utilize the load balancer's application-level health checks. When the Application Load Balancer target group marks the unresponsive instance as unhealthy, the Auto Scaling group detects this status, terminates the failed instance, and launches a new, healthy instance to maintain the desired capacity.
Adım Adım Çözüm
Anahtar Kavram
Auto Scaling Group Health Check Integration with Elastic Load Balancing