A startup is deploying a new API service on Amazon EC2 instances managed by an Auto Scaling group (ASG). The API service is configured to run on port 5000. An Application Load Balancer (ALB) is configured to route traffic to these instances. However, the ALB shows all targets in the target group as unhealthy. A solutions architect verifies that the API service is running on the instances. Which two configurations are required to resolve this issue and allow the ALB to perform successful health checks? (Select two.)
- Configure the target group health check settings to use port 5000 or the traffic port.Cevap
- Update the security group associated with the EC2 instances to allow inbound traffic on port 5000 from the security group of the Application Load Balancer.Cevap
- CConfigure a stateless Network ACL rule to allow inbound traffic on port 5000, assuming it will automatically allow the return traffic.
- DSet the target group health check port to default port 80 to ensure the Application Load Balancer can ping the web server.
- EConfigure an Amazon Route 53 latency routing policy to route the load balancer's health checks to the nearest EC2 instance.
Cevap
Configure the target group health check settings to use port 5000 or the traffic port, and update the security group associated with the EC2 instances to allow inbound traffic on port 5000 from the security group of the Application Load Balancer.
The Application Load Balancer must be configured to send health check requests to the port where the API service is listening, which is port 5000. Additionally, the security group for the EC2 instances must allow inbound traffic on port 5000 from the ALB's security group so the health check probes can successfully reach the instances.
Adım Adım Çözüm
Anahtar Kavram
Application Load Balancer health checks require alignment between the target group health check port configuration, the application listening port, and security groups that permit traffic from the load balancer.