A telemetry processing company is deploying an application on Amazon EC2 instances to analyze high-frequency sensor streams. The application components are distributed across multiple instances and require the lowest possible node-to-node network latency for internal synchronization. The external ingestion traffic is received on a custom TCP port 5050 via a Network Load Balancer (NLB). The instances do not run any web server on port 80. During initial deployment, the NLB marks all instances as unhealthy because the target group health checks are querying the default port 80. Which combination of actions will achieve the required network performance and resolve the health check issues?
- ALaunch the instances within a spread placement group, and modify the target group health check configuration to use port 5050.
- Launch the instances within a cluster placement group, and modify the target group health check configuration to use port 5050.Answer
- CLaunch the instances within a cluster placement group, and leave the target group health check configuration to use the default port 80.
- DLaunch the instances within a partition placement group, and leave the target group health check configuration to use the default port 80.
Answer
Launch the instances within a cluster placement group, and modify the target group health check configuration to use port 5050.
Launching the EC2 instances in a cluster placement group ensures that the instances are placed physically close to each other in the same Availability Zone, which minimizes node-to-node latency and maximizes network throughput. Correcting the target group health check port to use the custom application port ensures that the load balancer correctly validates the service's availability, allowing the instances to pass the health checks.
Step-by-Step Solution
Key Concept
Amazon EC2 Placement Groups and Elastic Load Balancing Health Checks
Estimated Time:1m 30s