A financial services company is deploying a distributed, real-time fraud detection engine on a fleet of Amazon EC2 instances. The engine requires high-throughput, low-latency node-to-node communication for parallel transaction analysis. The instances are registered with an Application Load Balancer (ALB). The fraud detection service listens on a custom port 8085, while a standard system logging daemon runs on port 80. The solutions architect needs to configure the environment to minimize inter-node network latency and ensure that the ALB only routes traffic to instances where the fraud detection service is actively running. Which two actions should the solutions architect take to meet these requirements? (Select TWO.)
- Launch the EC2 instances in a cluster placement group.Answer
- Configure the ALB target group health check to perform HTTP or TCP checks on port 8085.Answer
- CLaunch the EC2 instances in a spread placement group.
- DLaunch the EC2 instances in a partition placement group.
- EConfigure the ALB target group health check to perform HTTP or TCP checks on port 80.
Answer
To meet the performance and health monitoring requirements, launch the EC2 instances in a cluster placement group to achieve low-latency communication, and configure the Application Load Balancer target group health check to monitor port 8085 to verify the actual application status.
Launching the EC2 instances in a cluster placement group ensures they are located physically close to one another on the same underlying network fabric, yielding the lowest possible inter-node latency. Configuring the ALB target group health check to query the custom service port (8085) ensures that instances are marked as healthy only when the actual fraud detection service is running.
Step-by-Step Solution
Key Concept
Low-latency compute node orchestration using cluster placement groups coupled with service-aligned load balancer health checks.