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?

Question

Accepted Answer

C. Define an alias on the $LATEST version of the Lambda function. Update the API Gateway Defining an alias on the $LATEST version and configuring a routing weight on the alias allows a percentage of invocations to be directed to the new code. Because API Gateway is configured to invoke the alias ARN (which remains constant), the API Gateway URL does not change. This allows live production testing on a subset of traffic without any URL or integration updates.

Answer

A. Define a function version for the currently deployed production Lambda function. Update the API Publishing a function version and updating API Gateway to point directly at the new version routes 100% of traffic to the new code immediately, not a small canary percentage.

Answer

B. Define a function version for the currently deployed production Lambda function. Update the API Similar to A, pointing the API Gateway integration directly at a specific version with no alias routing configuration provides no mechanism for percentage-based traffic splitting.

Answer

D. Define a function version for the currently deployed production Lambda function. Update the API Creating a new Lambda function entirely results in a different ARN, which would require updating the API Gateway integration and consequently changes the observable behavior of the API endpoint configuration.

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…

Question

Options

How the community answered

Why each option

Community Discussion