You are working with several developers on migrating a web application from EC2 to API Gateway/Lambda serverless services. Previously, the deployment of EC2 instances has used a blue/green strategy by attaching new auto-scaling groups to a dedicated Elastic Load Balancer.

Answer options:

A.There is no straightforward way for API Gateway to implement canary deployment. Other service such as CodeDeploy is needed.
B.Use Elastic Beanstalk to deploy API Gateway/Lambda services as Elastic Beanstalk has supported a canary strategy when a new version is released for API Gateway/Lambda.
C.In the AWS Lambda console, when a new version is published, create a canary strategy to allocate 10% of the traffic to the new version. Add canary stage variables if needed.
D.Configure a canary strategy in the relevant API Gateway stage. For example, allocate 10% of the traffic to the new version. When a new API is deployed, select the stage with the enabled Canary.

Correct Answer – D
AWS API Gateway has supported canary deployment. In a canary release deployment, the API traffic is separated into a production release and a canary release with a user configured ratio. Check the details on API Gateway documentation https://docs.aws.amazon.com/apigateway/latest/developerguide/canary-release.html.
Option A is incorrect: Because although CodeDeploy may work as a canary deployment mode, it is unnecessary. API Gateway has a very easy method to set up a canary release.
Option B is incorrect: Because Elastic Beanstalk does not support canary deployment. Instead, it supports a blue/green deployment by switching environment URLs.
Option C is incorrect: Because Lambda does not support a canary method when a Lambda function is published. In this case, it should be done in API Gateway.
Option D is CORRECT: In API Gateway, canary settings can be found in the Stage. The Stage’s request distribution can be adjusted accordingly. For example: