How to deploy a lambda function using versioning and aliases + API Gateway

In this video we create a lambda function (a random number generator) and use versions and aliases to manage the deployment of the lambda function. ⚡️ Blog post: https://www.undefinedapps.com/post/de... 0:00 Intro: what are versions (numeric and $LATEST) and aliases and what are they useful for? 1:58 Iteration #1 - creating the lambda function, a new version, a new alias and an API Gateway endpoint url, which will trigger the function 5:45 Iteration #2 - create a new version and deploy the function by pointing the alias to the new version 6:59 Iteration #3 - A faster way to deploy the function and manage rollbacks, without using the aws console 11:18 Pointing an API gateway endpoint to trigger a lambda function's alias, instead of the $LATEST version ⚡️ Summary: The $LATEST version points to the latest version of the code of the function. For example, when you edit the code or upload a zip file with your code, the $LATEST version will immediately point to that version of the code. A numeric version of a function points to a snapshot of the function's code at the time when the version was released. This version of the code cannot be changed. An alias points to one of the versions of the function To manage the release and deployment of a lambda function, we can point an API Gateway endpoint to an alias and then when we release a new version of the function, adjust the alias to point to this new version. ⭐️ Subscribe for more content: https://newsletter.undefinedapps.com/ #AWS #Lambda #serverless