A company currently allows access to their API’s to customers via the API gateway. Currently, all clients have a 6-month period to move from using the older API’s to newer versions of the API’s. The code for the API is hosted in AWS Lambda. Which of the following is the ideal strategy to employ in such a situation?

Answer options:

A.Create another AWS Lambda version and give the link to that version to the customers.
B.Create another AWS Lambda ALIAS and give the link to that version to the customers.
C.Create another stage in the API gateway.
D.Create a deployment package that would automatically change the link to the new Lambda version.

Answer – C
The best way is to create a separate stage in the API gateway as maybe ‘v2’, and then customers could use both API versions. They can still slowly change their usage onto the new version in this duration.
Below is the concept of the API stage in the AWS Documentation.
API stage
"A logical reference to a lifecycle state of your API (for example, `dev`, `prod`, `beta`, `v2`). API stages are identified by API ID and stage name".
Options A and B are incorrect since access needs to be provided via the gateway.
Option D is incorrect since you need to keep both versions running side by side.
For more information on the API gateway, please refer to the below URL-
https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-basic-concept.html