What solution would allow the developer to perform a code push efficiently, without the need to update the API Gateway?
Associate different AWS Lambda functions to an API Gateway target endpoint.
Create different stages in API Gateway. then associate API Gateway with AWS Lambda.
Create aliases and versions in AWS Lambda.
Tag the AWS Lambda functions with different names.
Explanations:
Associating different AWS Lambda functions with an API Gateway endpoint requires manual changes to the API Gateway configuration for each new function version.
Creating different stages in API Gateway doesn’t solve the issue of dynamically updating Lambda versions without manual intervention.
Using aliases and versions in AWS Lambda allows the developer to create a stable alias that points to a specific Lambda version. This avoids the need to update API Gateway every time new code is pushed.
Tagging AWS Lambda functions with different names doesn’t address the need for API Gateway to dynamically point to the correct function version.
I infer that the answer is:
Create aliases and versions in AWS Lambda.