A company is creating a REST service using an Amazon API Gateway with AWS Lambda integration. The service must run different versions for testing purposes. What would be the BEST way to accomplish this?

Question

Accepted Answer

D. Deploy the API versions as unique stages with unique endpoints and use stage variables to Deploying each API version as a distinct stage (e.g., /v1, /v2, /test) gives each version its own endpoint URL and configuration. Stage variables act as key-value pairs that can reference different Lambda function aliases or versions per stage, enabling clean isolation between versions without duplicating API resources or requiring custom routing logic.

Answer

A. Use an X-Version header to denote which version is being called and pass that header to the Using a custom X-Version header requires the Lambda function itself to implement routing logic between versions, adding application complexity and coupling.

Answer

B. Create an API Gateway Lambda authorizer to route API clients to the correct API version. Lambda authorizers handle request authentication and authorization; they are not designed to route traffic between different API versions.

Answer

C. Create an API Gateway resource policy to isolate versions and provide context to the Lambda API Gateway resource policies control who can access the API (IP-based, account-based); they do not route requests to different Lambda versions.

A company is creating a REST service using an Amazon API Gateway with AWS Lambda integration. The service must run different versions for testing purposes. What would be the BEST way to accomplish…

Question

Options

How the community answered

Why each option

Community Discussion