Step by Step Procedure for Automating Lambda Deployment using Jenkins

Amazon provides end-to-end solutions for continuous integration and continuous deployment where its services like AWS CodeCommit, AWS CodeDeploy can be leveraged. You can also install Jenkins on EC2 and automate the deployments.

Jenkins is a great open-source automation server; Jenkins provides hundreds of plugins to support building, deploying, and automating any project. Here we are going to discuss the approach where Jenkins is used as a simple CI server and to automate the AWS Lambda invocation and deployment

We are leveraging a plugin that will help us to have the above use case achieved.

Flow Diagram:

Prerequisites:

Follow the official documentation to have it installed: Jenkins running on EC2

Step by Step Guide:

Step 1: AWS Lambda plugin installation

1. Search and install for AWS Lambda plugin in available plugins by clicking Manage Jenkins and Manage Plugins
   
   

Step 2: IAM Set up

1. For deployment and invocation, we need access to the GetFunction, CreateFunction, UpdateFunctionCode and UpdateFunctionConfiguration, InvokeFunction
2. We need access to iam:PassRole to attach a role to the Lambda.
   IAM policy

   { "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1432812345671", "Effect": "Allow", "Action": [ "lambda:GetFunction", "lambda:CreateFunction", "lambda:UpdateFunctionCode", "lambda:UpdateFunctionConfiguration", "lambda:InvokeFunction" ], "Resource": [ "arn:aws:lambda:REGION:ACCOUNTID:function:FUNCTIONNAME" ] }, { "Sid": "Stmt14328112345672", "Effect": "Allow", "Action": [ "iam:Passrole" ], "Resource": [ "arn:aws:iam::ACCOUNTID:role/FUNCTIONROLE" ] } ] }

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

   {     "Version": "2012-10-17",     "Statement": [         {             "Sid": "Stmt1432812345671",             "Effect": "Allow",             "Action": [                 "lambda:GetFunction",                 "lambda:CreateFunction",                 "lambda:UpdateFunctionCode",                 "lambda:UpdateFunctionConfiguration", "lambda:InvokeFunction"               ],             "Resource": [                 "arn:aws:lambda:REGION:ACCOUNTID:function:FUNCTIONNAME"             ]         },         {             "Sid": "Stmt14328112345672",             "Effect": "Allow",             "Action": [                 "iam:Passrole"             ],             "Resource": [                 "arn:aws:iam::ACCOUNTID:role/FUNCTIONROLE"             ]         }     ] }

3. Replace ACCOUNTID, FUNCTIONROLE accordingly in the policy. This Instance profile role with policy can be attached to the EC2 instance on which Jenkins is running.

Step 3: Jenkins Job Configuration

1. Create a Maven project with Java source code repo details.
2. Build and test code as per requirement
3. In post-build steps add AWS Lamba deployment
4. Configure required details like AWS Region, Function Name, Role, zip location (generated jar which is built). AWS keys are not required as we are using the Instance role
5. We can also configure environment variables, subnets if we configure lambda within VPC. Please check Use Instance credentials to have instance role leveraged
6. Done!!! Save and Build Job to have your lambda created

Conclusion:

By following the above process, you can have continuous deployment into our lambda functions wherever there is a code change with test cases and code quality checks.

For more DevOps, and CICD content, stay tuned to this page. If you have any queries about the CICD process, post them in the below comment section and I will get back to you at the earliest.

About CloudThat