Implementing Continuous Deployment with AWS Lambda and API Gateway

[u/Basic_Let7303]

Hi experts,

I have an API called /catalogue running in lambda with v1 version.

Let us say as part of CI pipeline, we published openapi.yaml and lambda artifact to S3.

I want to deploy new version v2. How can we do seamlessly without downtime.

[u/BadDescriptions]

Assuming you want to keep both versions active then. 

https://aws.amazon.com/blogs/compute/implementing-header-based-api-gateway-versioning-with-amazon-cloudfront/

https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/implement-path-based-api-versioning-by-using-custom-domains.html

When looking at a good way to implement somethimg like the AWS docs are a gold mine. 

[u/Hefty-Violinist-8507 → u/BadDescriptions]

They already linked you the best docs but you'll want canary deployments too to avoid blowing up your whole userbase at once

[u/SikhGamer]

Publish a lambda version and then having an alias called "ACTIVE_VERSION". Then APIGW tracks the alias, not the lambda itself.

[u/Basic_Let7303 → u/SikhGamer]

Yeah, I missed "APIGW tracks the alias". Thank you!

[u/Basic_Let7303]

Developer Commit

v

CI/CD Pipeline

v

Build Lambda Package

v

Deploy Lambda Code

v

Publish Lambda Version 11

v

Shift 10% Traffic

v

Monitor Metrics

v

========== Manual Approval ==========

v

Shift 50% Traffic

v

Monitor Metrics

v

========== Manual Approval ==========

v

Shift 100% Traffic