A gaming company hosts a mobile leaderboard application on Amazon EC2 instances in an Auto Scaling group (ASG). The instances are registered with a target group for an Application Load Balancer (ALB). The leaderboard application listens on custom TCP port , but the ALB shows all EC2 instances as unhealthy. A solutions architect verifies that the application is running correctly on the instances. Which two actions should the solutions architect take to resolve the health check issues? (Select two.)
- Update the ALB target group health check configuration to use port or select the traffic port option.Answer
- Configure the security group of the EC2 instances to allow inbound TCP traffic on port from the security group of the ALB.Answer
- CModify the target group health check port to port because Application Load Balancers can only perform HTTP health checks on standard web ports.
- DRemove all outbound rules from the subnet's Network ACL because Network ACLs are stateful and will automatically allow return traffic.
- EChange the Amazon Route 53 routing policy to Latency routing pointing directly to the EC2 instances to bypass the Application Load Balancer.
Answer
To resolve the health check issues, the target group health check port must match the application port (port ), and the EC2 instances' security group must permit inbound traffic on port from the load balancer.
The correct actions are to update the target group health check to query the custom port (or select the traffic port option) and configure the EC2 instances' security group to allow inbound traffic on port from the ALB's security group. This ensures the load balancer can reach the application to evaluate its health and forward client traffic.
Step-by-Step Solution
Key Concept
Auto Scaling and Elastic Load Balancing health check configuration and security group alignment