Which solution will meet these requirements?
Update the Route 53 records to use a latency routing policy. Add a static error page that is hosted in an Amazon S3 bucket to the records so that the traffic is sent to the most responsive endpoints.
Set up a Route 53 active-passive failover configuration. Direct traffic to a static error page that is hosted in an Amazon S3 bucket when Route 53 health checks determine that the ALB endpoint is unhealthy.
Set up a Route 53 active-active configuration with the ALB and an Amazon EC2 instance that hosts a static error page as endpoints. Configure Route 53 to send requests to the instance only if the health checks fail for the ALB.
Update the Route 53 records to use a multivalue answer routing policy. Create a health check. Direct traffic to the website if the health check passes. Direct traffic to a static error page that is hosted in Amazon S3 if the health check does not pass.
Explanations:
While updating the Route 53 records to use a latency routing policy may improve response times by directing traffic to the most responsive endpoints, it does not provide a failover solution for directing users to a backup static error page when the primary website is unavailable.
Setting up a Route 53 active-passive failover configuration allows for directing traffic to a static error page hosted in an S3 bucket when health checks determine that the ALB endpoint is unhealthy. This meets the requirement of minimizing changes and infrastructure overhead while ensuring availability.
An active-active configuration with both the ALB and an EC2 instance increases complexity and infrastructure overhead, as it requires managing two endpoints simultaneously. It does not specifically address directing traffic to a static error page when the ALB is unavailable, as it relies on health checks to determine which endpoint to use.
Although using a multivalue answer routing policy with health checks can route traffic appropriately, it does not guarantee failover to a static error page when the ALB is unavailable. The multivalue routing does not inherently provide a dedicated fallback mechanism like active-passive failover does.
It appears that the answer is:
Set up a Route 53 active-passive failover configuration. Direct traffic to a static error page that is hosted in an Amazon S3 bucket when Route 53 health checks determine that the ALB endpoint is unhealthy.
I figure that the answer is:
Set up a Route 53 active-passive failover configuration. Direct traffic to a static error page that is hosted in an Amazon S3 bucket when Route 53 health checks determine that the ALB endpoint is unhealthy.