A company is hosting a single-page web application in the AWS Cloud. The company is using Amazon CloudFront to reach its goal audience. The CloudFront distribution has an Amazon S3 bucket that is conf

Creating a second CloudFront distribution for the new version of the application allows for independent deployment and serving of the updated static files. By then updating the Amazon Route 53 A record with a weighted routing policy, traffic can be precisely split between the two CloudFront distributions (old and new versions), enabling a controlled canary release.

While Lambda@Edge can modify requests, implementing a complex weighted routing algorithm directly within a Lambda@Edge function for canary deployments of static content is less efficient and more complex than leveraging Amazon Route 53's native weighted routing capabilities, which are designed for this exact purpose.

This option correctly describes setting up the infrastructure for a new version (second S3, second origin), but then proposes using Lambda@Edge to forward headers/cookies for traffic splitting. This is not the standard or most efficient way to perform weighted canary routing of static websites, as Route 53's weighted routing is more suitable for directing traffic to different CloudFront distributions.

Lambda@Edge functions are designed for modifying requests and responses at the edge, not for directly serving or hosting entire web application versions from scratch, as the static files for the application reside in S3 and are served via CloudFront.