Which solution meets these requirements?
Provision a full, secondary application deployment in a different AWS Region. Update the Route 53 A record to be a failover record. Add both of the CloudFront distributions as values. Create Route 53 health checks.
Provision an ALB, an Auto Scaling group, and EC2 instances in a different AWS Region. Update the CloudFront distribution, and create a second origin for the new ALCreate an origin group for the two origins. Configure one origin as primary and one origin as secondary.
Provision an Auto Scaling group and EC2 instances in a different AWS Region. Create a second target for the new Auto Scaling group in the ALB. Set up the failover routing algorithm on the ALB.
Provision a full, secondary application deployment in a different AWS Region. Create a second CloudFront distribution, and add the new application setup as an origin. Create an AWS Global Accelerator accelerator. Add both of the CloudFront distributions as endpoints.
Explanations:
This solution requires a full, secondary application deployment, but it doesn’t properly handle traffic failover between CloudFront distributions. While Route 53 can route traffic based on health checks, this does not ensure automatic failover at the CloudFront level for high availability.
This solution provisions an ALB and Auto Scaling group in a second AWS Region and adds a second CloudFront origin. The origin group configuration in CloudFront allows automatic failover between the two regions, ensuring high availability.
ALBs cannot have target groups in different AWS Regions. The failover routing algorithm is not supported on the ALB for cross-region failover, making this solution infeasible for high availability across regions.
This solution requires a second CloudFront distribution and AWS Global Accelerator, which is unnecessary for a simple high-availability setup. While Global Accelerator can provide improved global access, it introduces unnecessary complexity compared to using CloudFront’s origin groups for automatic failover.
I rate that the answer is:
Provision an ALB, an Auto Scaling group, and EC2 instances in a different AWS Region. Update the CloudFront distribution, and create a second origin for the new ALCreate an origin group for the two origins. Configure one origin as primary and one origin as secondary.