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

[@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

[@FedericoTartarini]

Glad it was helpful!

[@mymacaintwag]

What is the deploy functionality for in the api gateway?

[@abidmehmood1150]

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

[@pr0mming]

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?