What is the SIMPLEST solution for the developer to use for rolling out the new API version to a limited number of users through API Gateway?
Create a new API in API Gateway. Direct a portion of the traffic to the new API using an Amazon Route 53 weighted routing policy.
Validate the new API version and promote it to production during the window of lowest expected utilization.
Implement an Amazon CloudWatch alarm to trigger a rollback if the observed HTTP 500 status code rate exceeds a predetermined threshold.
Use the canary release deployment option in API Gateway. Direct a percentage of the API traffic using the canarySettings setting.
Explanations:
Creating a new API and using Route 53 for traffic management adds complexity and is not a transparent way to roll out changes. It involves setting up a separate API and managing two APIs, which is not optimal for gradual rollouts.
Promoting the new API version during low utilization does not allow for gradual rollout or controlled testing with real users. It risks impacting all users immediately if issues arise, making it a less safe approach.
Implementing a CloudWatch alarm for rollbacks does not provide a way to gradually introduce the new API version. It only reacts to problems after they occur and does not facilitate controlled testing with a limited user base.
Using the canary release deployment option in API Gateway allows the developer to route a percentage of traffic to the new API version while keeping the rest on the old version. This enables safe and gradual testing, making it the simplest and most effective solution for controlled rollouts.
I scheme that the answer is:
Use the canary release deployment option in API Gateway. Direct a percentage of the API traffic using the canarySettings setting.