QuestionQ75

VerifiedDeployment

A developer is optimizing an AWS Lambda function and wants to test the changes in production on a small percentage of all traffic. The Lambda function serves requests to a RE ST API in Amazon API Gateway. The developer needs to deploy their changes and perform a test in production without changing the API Gateway URL.

Which solution will meet these requirements?

Explanation

Pointing the API Gateway integration at a Lambda alias (rather than a specific numbered version) means the integration's target reference never has to change again; only the alias's underlying version needs to move as new code is published. Combining that stable alias reference with an API Gateway canary release on the production stage lets a defined percentage of traffic reach the newly published code while the base stage continues serving the prior version, all without altering the API's public URL. Referencing a fixed function version directly in the integration (A, B, D) means every code update requires re-pointing the integration to a new version number, adding operational overhead that the alias-based approach avoids. Learn more: Configuring a Lambda function to handle canary deployment

Community Discussion

No comments yet. Be the first to start the discussion!