Showing posts from September, 2019

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 descriptio

Deploy Java Lambda - AWS

This post walks through steps required to create and deploy java lambda functions using eclipse. In the next post, we will have a look at release management and versioning of lambdas. We will be using Eclipse for this example. AWS tool kit plugin is not mandatory to create java lambda functions, but it is handy to have it installed. This post assumes that AWS plugin is installed in eclipse. Click File -> New -> Other -> aws and then select ‘AWS Lambda Java Project’. Enter name of project ‘LambdaExamples’ and click Finish. Lambda Project has been created and lambda functions can now be created in this project. Again click File -> New -> Other -> aws and then select ‘AWS Lambda Function’. Enter source folder, package name and name of lambda function. Also select type of event which this lambda will receive. Lambdas are usually triggered as part of some event. For example, a new file uploaded to S3, or a new message arrived in SNS Topic. AWS pass