How should the company deploy this solution?
Use Amazon S3 website hosting for the backup website and Route 53 failover routing policy.
Use Amazon S3 website hosting for the backup website and Route 53 latency routing policy.
Deploy the application in another AWS Region and use ELB health checks for failover routing.
Deploy the application in another AWS Region and use server-side redirection on the primary website.
Explanations:
Amazon S3 website hosting can be used for a simple backup page, and Route 53 failover routing can switch traffic to the backup site when the primary site is down based on health checks.
Latency routing does not support failover based on health status, and it is designed for routing traffic to the lowest-latency region, not for backup purposes.
Deploying the application in another AWS Region with ELB health checks does not address the requirement of a simple backup message with contact details when the primary site is down.
Server-side redirection on the primary website would not meet the goal of providing a backup website with a message and contact details; it is not an efficient or suitable approach for failover.
As I see it, the answer is:
Use Amazon S3 website hosting for the backup website and Route 53 failover routing policy.
I believe the answer is:
Use Amazon S3 website hosting for the backup website and Route 53 failover routing policy.