A company hosts a microservice on Amazon EC2 instances inside private subnets. The instances are managed by an Auto Scaling group (ASG) behind a public Application Load Balancer (ALB). The microservice is configured to listen on TCP port 8080. The ALB target group is configured to send health check requests to the instances on port 8080. After a security audit, a network engineer modified the custom network access control list (network ACL) associated with the private subnets. Shortly after, the ALB target group health checks began failing, marking all EC2 instances as unhealthy. The security group associated with the EC2 instances correctly allows inbound traffic on port 8080 from the ALB's security group. Which action should the solutions architect take to resolve this issue and restore service availability?
- AModify the target group health check configuration to query port 80 instead of port 8080 to align with the Application Load Balancer's public listener.
- BAdd an outbound rule to the EC2 instances' security group that explicitly allows return traffic to the Application Load Balancer on ephemeral ports.
- Update the subnet network ACL to allow outbound traffic on ephemeral ports (1024-65535) to the load balancer's subnets.Cevap
- DCreate an Amazon Route 53 Latency routing policy pointing directly to the EC2 instances' private IP addresses to bypass the load balancer's health checks.