What should a solutions architect implement to overcome these timeout errors?
Create a Route 53 simple routing policy record for each EC2 instance. Associate a health check with each record.
Create a Route 53 failover routing policy record for each EC2 instance. Associate a health check with each record.
Create an Amazon CloudFront distribution with EC2 instances as its origin. Associate a health check with the EC2 instances.
Create an Application Load Balancer (ALB) with a health check in front of the EC2 instances. Route to the ALB from Route 53.
Explanations:
Simple routing policy in Route 53 does not consider instance health. Associating health checks with each individual EC2 instance would not effectively handle routing traffic to healthy instances automatically.
Failover routing policy requires specifying a primary and secondary record for routing. While health checks are involved, this approach is meant for failover scenarios and not for balancing traffic among multiple healthy instances.
CloudFront is primarily used for content delivery and caching, not for load balancing or managing EC2 instance health directly. Health checks on CloudFront would not address the root cause of unhealthy EC2 instances.
An Application Load Balancer (ALB) with health checks ensures that only healthy EC2 instances are receiving traffic. Route 53 can direct traffic to the ALB, which automatically routes to healthy instances, solving the timeout issue.
As far as I can tell, the answer is:
Create an Application Load Balancer (ALB) with a health check in front of the EC2 instances. Route to the ALB from Route 53.
I suspect that the answer is:
Create an Application Load Balancer (ALB) with a health check in front of the EC2 instances. Route to the ALB from Route 53.