A solutions architect is deploying a web application on Amazon EC2 instances managed by an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The application runs on a custom port 8080. The security group of the EC2 instances allows inbound traffic only from the ALB's security group on port 8080. The solutions architect needs to configure the environment so that unhealthy instances are automatically detected and replaced by the ASG. Which TWO configurations should the solutions architect perform to meet these requirements? (Select TWO.)
- Configure the target group health check port to use the traffic port or port 8080.Cevap
- Configure the Auto Scaling group to use Elastic Load Balancing (ELB) health checks.Cevap
- CKeep the default target group health check port 80 and let the load balancer automatically forward the health checks to port 8080.
- DModify the subnet's stateless Network ACL (NACL) to automatically track and allow return traffic from the load balancer's health checks.
- EConfigure an Amazon Route 53 Latency routing policy to target the private IP addresses of the EC2 instances directly for health checks.
Cevap
Configure the target group health check port to use the traffic port or port 8080, and configure the Auto Scaling group to use Elastic Load Balancing (ELB) health checks.
To ensure correct application health detection and automatic recovery, the Solutions Architect must perform two actions. First, the Application Load Balancer target group must perform health checks on the actual port where the application is listening (port 8080) because the security group blocks other ports such as the default port 80. Second, the Auto Scaling group must have its health check type set to 'ELB' so it can receive health check failures from the load balancer and automatically replace unhealthy instances.
Adım Adım Çözüm
Anahtar Kavram
ELB health checks integrated with Auto Scaling groups for custom application ports.