Invoke Lambda aliases linked to a version using stage variables in AWS API Gateway

I explain how to create a simple Lambda function, which uses versions and aliases. Then I demonstrate how to invoke specific aliases by connecting them to a single AWS API Gateway using stage variables.

✅ Let's connect:

🎥 Content of this video:
00:00 - What you will learn
03:50 - Create an AWS Lambda function
05:14 - Test the Lambda function
06:00 - Create a version of the function
06:20 - Create an alias
08:50 - Create an AWS API Gateway
10:20 - Create a resource
10:50 - Create a method with stage variables
13:40 - Deploy API and create stages
14:30 - Add stage variables to the stages

🔣 Keywords:
#awslambda #awsapigateway #awslambdaversion #lambdaaliases #aws #apigateway #lambda

[romihans]

Thank you very much for a very good explanation on using stage variables for implementing different versions of Lambda code for test, dev, production etc. I was able to implement this though at firs the new UI of AWS API was slightly confusing. But this works very well. This is one of the few resources I have found on the topic

[mymacaintwag]

What is the deploy functionality for in the api gateway?

[prmming]

Nice video but how get this with S3 Events instead Gateway way? I mean, I have a Lambda that will be trigger by a S3 in specific bucket (COPY action), I use database connections inside my Lambda code but the connection strings for my database are in the Lambda Environment variables, I need 3 different connection strings (dev, prod, qa) so I guess I need 3 different versions, but when I publish a new version I am not able for edit the the environment variables in the new version, so I need reedit the $LATEST code and publish my prod code version for example, and rollback the variables in my $LATEST, this is annoying, do you now a better way for manage this?

[abidmehmood]

how we can update version with pipeline? thats what i need