Blue Green with Static S3 Website

Question

A customer has an angular serverless app that is hosted on S3.  There are looking to set up a Blue Green deployment strategy and explored using route53 weighted routes to two CloudFront distributions.  The customer get a CNAMEAlreadyExists error and I came across this link - https://aws.amazon.com/premiumsupport/knowledge-center/resolve-cnamealreadyexists-error/

Looking at using Lambda@Edge as a solution like in the following link - https://aws.amazon.com/blogs/networking-and-content-delivery/truecars-dynamic-routing-with-aws-lambdaedge/

How are other customers doing Blue Green deployments with static s3 websites?

Accepted Answer

Lambda@Edge (on origin request event) is your answer to route requests to different website variations on an s3 bucket. however, it's up to you how do you want to do the routing logic itself. For ex:
* If you want to have stickiness, then you should use Lambda@Edge also on viewer response event to set a cookie. forward this cookie in Cloudfront and use your Lambda@Edge router function to select the correct version.
* In the Lambda@Edeg router, you can make a network call to an external georgraphy replicated endpoint to to decide about the load balancing percentage. Replicated endpoints possibilities: dynamoDB global tables or Route 53 TXT records.

Blue Green with Static S3 Website

Contenus pertinents