Lambda Alias and Versions

In the previous post, we looked at creating and deploying lambda functions. Deploying lambda functions is relatively straight forward. However, deployments can get tricky when there are many lambda functions, function code changes are frequent, and releases need to be tracked appropriately. This is where Lambda Aliases and Lambda Versions can make life easier. There are three elements and understanding these can help to refine lambda deployment process.
Lambda Function:
Lambda function refers to actual piece of code being deployed. This is function which gets executed when lambda is invoked. Every lambda function can be uniquely identified by ARN.
Lambda Version:
As name suggests, Lambda version refers to version of lambda function. One lambda function can have many lambda versions and every version gets a unique ARN (by appending version as suffix to actual lambda ARN). Every time you make a change in lambda function, you can create a new version and add relevant description to i…
Lambda Function:
Lambda function refers to actual piece of code being deployed. This is function which gets executed when lambda is invoked. Every lambda function can be uniquely identified by ARN.
Lambda Version:
As name suggests, Lambda version refers to version of lambda function. One lambda function can have many lambda versions and every version gets a unique ARN (by appending version as suffix to actual lambda ARN). Every time you make a change in lambda function, you can create a new version and add relevant description to i…