Which solution will meet these requirements?
Enable a Lambda authorizer for the Lambda function alias in API Gateway. Republish PROD and create a new stage for DEV. Create API Gateway stage variables for the PROD and DEV stages. Point each stage variable to the PROD Lambda authorizer to the DEV Lambda authorizer.
Set up a gateway response in API Gateway for the Lambda function alias. Republish PROD and create a new stage for DEV. Create gateway responses in API Gateway for PROD and DEV Lambda aliases.
Use an environment variable for the Lambda function alias in API Gateway. Republish PROD and create a new stage for development. Create API gateway environment variables for PROD and DEV stages. Point each stage variable to the PROD Lambda function alias to the DEV Lambda function alias.
Use an API Gateway stage variable to configure the Lambda function alias. Republish PROD and create a new stage for development. Create API Gateway stage variables for PROD and DEV stages. Point each stage variable to the PROD Lambda function alias and to the DEV Lambda function alias.
Explanations:
Enabling a Lambda authorizer does not facilitate the simultaneous invocation of Lambda function versions through API Gateway. Additionally, the approach does not directly address the requirement for separate access to PROD and DEV environments.
Setting up a gateway response does not meet the requirement to distinctly invoke different Lambda function aliases simultaneously. Gateway responses are used for customizing error responses rather than routing requests to different function versions.
Using environment variables does not provide the necessary distinction for invoking separate Lambda function aliases. API Gateway environment variables are not used for configuring Lambda aliases; instead, stage variables are intended for that purpose.
Using API Gateway stage variables allows for the configuration of distinct Lambda function aliases for each stage (PROD and DEV). This approach enables API Gateway to route requests to the appropriate Lambda function based on the stage being accessed, meeting the requirement for simultaneous and distinct availability.
I measure that the answer is:
Use an API Gateway stage variable to configure the Lambda function alias. Republish PROD and create a new stage for development. Create API Gateway stage variables for PROD and DEV stages. Point each stage variable to the PROD Lambda function alias and to the DEV Lambda function alias.