Why you should use AWS Lambda's Aliases

[@Jonathan.Davies]

Not going to lie, I was pretty proud of this thumbnail. Does anyone understand what I was trying to do? (I wouldn't blame you if you don't 🤣)

[@Gustavo-uc9rr]

Hi Jon, very clear explanation. Assuming that we're using alias as environments, can we set env variables for each alias? In my case I'm developing some services and I got two DynamoDB tables, one for staging (already running and populated) and now I'm implementing the production environment. I've already implemented the alias but now I wanna set env vars so staging Alias points to staging DynamoDB table and the production alias points to production DynamoDB table. I see that we can set up env vars in the lambda function (main/latest version) and these variables are replicated to the versions, if we were able to change the value of the env var for every new version (before pointing the production alias to the new version) it would solve my problem but we don't have this option. I'd appreciate if you could give me any clue. Thank you!

[@denystreltsov1465]

keep doing videos.

[@Jonathan.Davies]

Will do, appreciate the nice comment Deny 👍