A software development company is launching a new REST API deployed on Amazon EC2 instances within an Auto Scaling group. The API application is configured to listen on port . An Application Load Balancer (ALB) is deployed to distribute incoming traffic across the instances. The Solutions Architect needs to configure the load balancer and security settings to ensure the ALB can successfully perform health checks and route traffic to the application. Which TWO configurations should the Solutions Architect implement? (Select two).
- Set the target group health check port to 'traffic-port' or explicitly define it as port .Answer
- Allow inbound TCP traffic on port in the EC2 instance security group, sourcing from the Application Load Balancer's security group.Answer
- CLeave the target group health check port at the default port and rely on the load balancer to automatically redirect requests to port .
- DConfigure the subnet Network Access Control List (NACL) to be stateful and allow inbound traffic on port .
- EConfigure a Route 53 latency routing policy to dynamically detect and remove unhealthy EC2 instances from the target group.
Answer
The Solutions Architect must configure the target group health check port to use the traffic port (or explicitly port 5000) and update the EC2 instance security group to allow inbound TCP traffic on port 5000 from the Application Load Balancer's security group.
For an application listening on a custom port like port 5000, the Application Load Balancer must be configured to send health check requests to that specific port (or use the 'traffic-port' option). Additionally, the EC2 instances' security group must allow inbound traffic on port 5000 from the ALB's security group to permit health checks and application traffic to flow.
Step-by-Step Solution
Key Concept
Configuring load balancer target groups and instance security groups for custom port applications to ensure proper health monitoring and routing.