A developer has updated an API hosted on Amazon API Gateway. To minimize the risk of the new version affecting users, the developer wants to test the update by routing of the incoming API calls to the new version, while the remaining of the traffic goes to the current version. The developer wants to monitor the performance of the new version using CloudWatch and easily promote it to full production once verified. Which approach meets these requirements with the least operational complexity?
- Configure a canary release on the existing API Gateway stage, set the canary traffic percentage to , and promote the canary after verification.Cevap
- BDeploy the new API version to a new stage, and configure an AWS Lambda function with alias routing to split the traffic between the stages.
- CDeploy the new API version to a new stage, and configure Amazon Route 53 weighted routing to distribute the traffic between the two stage endpoints.
- DCreate a second API Gateway API, deploy it, and place both APIs behind an Application Load Balancer with weighted target groups.
Cevap
Configure a canary release on the existing API Gateway stage, set the canary traffic percentage to , and promote the canary after verification.
The correct answer is to configure a canary release on the existing API Gateway stage. When a canary release is enabled, API Gateway automatically routes a specified percentage of API traffic (in this case, ) to the new deployment. The developer can monitor the performance of this canary using Amazon CloudWatch metrics and easily promote it to the production release once verified, which requires the least operational effort.
Adım Adım Çözüm
Anahtar Kavram
API Gateway Canary Deployments
Tahmini Süre:1m 30s