A company is releasing a new version of an API microservice deployed on AWS Lambda. The deployment pipeline uses AWS CodeDeploy to manage traffic shifting. To minimize risk, the Solutions Architect wants to route of the traffic to the new Lambda version immediately, and then increase the traffic by another every minutes until the transition is complete. If the error rate exceeds a specified threshold, the deployment must roll back automatically. Which deployment configuration should the Solutions Architect configure in the CodeDeploy deployment group to achieve this transition?
- CodeDeployDefault.LambdaLinear10PercentEvery10MinutesAnswer
- BCodeDeployDefault.LambdaCanary10Percent10Minutes
- CCodeDeployDefault.LambdaLinear10PercentEvery1Minute
- DCodeDeployDefault.LambdaAllAtOnce
Answer
CodeDeployDefault.LambdaLinear10PercentEvery10Minutes
The configuration stating 'CodeDeployDefault.LambdaLinear10PercentEvery10Minutes' is correct because linear configurations shift traffic in equal increments at regular intervals. A linear shift every minutes matches the requirement to scale traffic by initially and then by another every minutes.
Step-by-Step Solution
Key Concept
AWS CodeDeploy deployment configurations define the way traffic is shifted to new versions of Lambda functions or ECS tasks. Linear deployments shift traffic in equal increments over time, while canary deployments shift a small percentage first and then shift the remainder all at once.