Learn how to release new API versions with minimal impact and data loss using the canary release deployment stage in AWS API Gateway, allowing safe testing and rollback before production deployment.
Table of Contents
Question
A retail company uses a regional Amazon API Gateway API for its public REST APIs. The API Gateway endpoint is a custom domain name that points to an Amazon Route 53 alias record. A solutions architect needs to create a solution that has minimal effects on customers and minimal data loss to release the new version of APIs.
Which solution will meet these requirements?
A. Create a canary release deployment stage for API Gateway. Deploy the latest API version. Point an appropriate percentage of traffic to the canary stage. After API verification, promote the canary stage to the production stage.
B. Create a new API Gateway endpoint with a new version of the API in OpenAPI YAML file format. Use the import-to-update operation in merge mode into the API in API Gateway. Deploy the new version of the API to the production stage.
C. Create a new API Gateway endpoint with a new version of the API in OpenAPI JSON file format. Use the import-to-update operation in overwrite mode into the API in API Gateway. Deploy the new version of the API to the production stage.
D. Create a new API Gateway endpoint with new versions of the API definitions. Create a custom domain name for the new API Gateway API. Point the Route 53 alias record to the new API Gateway API custom domain name.
Answer
A. Create a canary release deployment stage for API Gateway. Deploy the latest API version. Point an appropriate percentage of traffic to the canary stage. After API verification, promote the canary stage to the production stage.
Explanation
Canary Release Deployment Stage: API Gateway supports creating a canary release deployment stage, which is a separate stage for testing new API versions before promoting them to production. This allows you to release new API versions with minimal impact on customers and minimal data loss.
Deploy the Latest API Version: First, you deploy the latest version of the API to the canary release deployment stage. This stage runs in parallel with the existing production stage, but with a small percentage of traffic routed to it.
Point Traffic to the Canary Stage: You can configure the canary stage to receive a specific percentage of traffic from the custom domain name associated with the API Gateway endpoint. This allows you to test the new API version with a subset of real user traffic.
API Verification: During the canary release, you can monitor and verify the new API version’s behavior, performance, and correctness. If any issues are detected, you can roll back the changes without impacting all users.
Promote Canary Stage to Production: Once you have verified the new API version and are confident in its stability, you can promote the canary stage to the production stage. This process updates the production stage with the new API version and routes all traffic to the updated production stage.
By using the canary release deployment stage, you can minimize the impact on customers and potential data loss during the API update process. Only a small percentage of users will be affected during the testing phase, and you can safely roll back or promote the changes based on the verification results.
Amazon AWS Certified Solutions Architect – Associate SAA-C03 certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Amazon AWS Certified Solutions Architect – Associate SAA-C03 exam and earn Amazon AWS Certified Solutions Architect – Associate SAA-C03 certification.