setup 1-box stage in lambda ci-cd pipeline

Question

One box stage in CICD pipeline is a stage before production stage. This stage also will receive the production traffic. The goal of this stage is to validate the new changes with very small prod traffic and keep the blast radius to minimal incase of issues.

In server based deployment, this stage will contain only 1 machine to receive very small % of traffic. The code changes will be deployed to 1-box stage before production and leave it for some time to validate the behaviour of new change.  If there is an issue in 1-box stage with the new code, the blast radius will be minimal and roll back is faster since the changes are deployed in only one machine.

It is explained in "Backward compatibility and one-box testing" topic in this link - https://aws.amazon.com/builders-library/automating-safe-hands-off-deployments/

How do we setup the same in lambda ci-cd ? Any leads on this will be super helpful.

Accepted Answer

With Lambda you don't really have boxes, however, you can easily route a small percentage of your traffic to a new version and later increase that percentage all the way to 100% or decrease it to 0%. You can do this using [Alias routing configuration](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html#configuring-alias-routing). CodeDeploy supports different [traffic shifting options](https://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-configurations.html).

setup 1-box stage in lambda ci-cd pipeline

Relevant content