Create an AWS Lambda function from an Octopus Deployment

AWS Lambda is one of the AWS Compute Services, alongside with Amazon EC2 or Amazon EC2 Container Service. In a nutshell, AWS Lambda is the serverless offer from AWS, allowing “you run code without provisioning or managing servers”[1].

In the DevOps spirit, and using Octopus as the Continuous Deployment tool, I couldn’t find a step template to create an AWS Lambda function. If it doesn’t exist, create it and give it away!

Background

AWS Lambda supports a broad range of technologies, such as Java, Python or NodeJS. The new kid on the block was .NET Core, announced on 1st of December 2016. It was a good announcement for Microsoft tech shops, having another tool in the toolbelt.

The tools used for this demo were:

Visual Studio and AWS Lambda Function Project

Using one of the Visual Studio AWS Lambda templates for the demo, the project was created and committed here. In a nutshell, the AWS Lambda function receives an Amazon S3 event and returns the S3 object Content Type. Simple and straightforward.

Continuous Integration Server

You can use your preferred CI server. In your CI server will need to:

  1. Publish the AWS Lambda .NET project
    dotnet publish AWSLambdaDemo -c Release
  2. Zip the published AWS Lambda .NET project
  3. Create the NuGet package for Octopus
    Octo.exe pack --id AWSLambdaDemo --version 1.0.0.0
  4. Upload the AWS Lambda NuGet package to Octopus Server
    NuGet.exe push AWSLambdaDemo.1.0.0.0.nupkg -ApiKey myApiKey -Source https://myOctopusServer

These instructions are generic, and depending on your CI server technology can be done in different ways. You can take them as generic steps, and adapt to your needs.

 Create AWS Lambda function Octopus step template

The step template is simple and straightforward. The Powershell script:

  1. Checks if the AWS Tools for Windows Powershell is installed
  2. Get all the required parameters, such as the access keys, region, function name, among others
  3. Validate the parameters, e. g., if they have a value
  4. Execute the operation
  5. Feedback the user

The step template has a prerequisite, it depends on the AWS Tools for Windows Powershell. You need to download and install it on the machines where the step will run.

Octopus Project

To create the AWS Lambda function, we need to use a pivot machine. At the moment is not possible to publish it directly to AWS.

octopus2awslambda

We will use the Octopus out-of-the-box features to deploy the AWSLambdaDemo package to the Pivot Machine, and the new step template to publish the function to AWS.

The Demo Octopus Project will look like this:

octopus-project

The first step just deploys the upload NuGet AWSLambdaDemo package to a custom location in the Pivot Machine (with the role AWS Lambda Demo).

The second step creates the AWS Lambda from the deployed NuGet AWSLambdaDemo package from the custom location.

octopus-aws-step

After creating a release (potentially triggered by the CI server), Octopus Server can deploy it.

octopus-aws-deploy

And voilá! A new AWS Lambda function is deployed!

aws-lambda

Final thoughts

The step template is under the Octopus Library OSS. You can fork and add new features to it, or open an issue in my fork. All suggestions are welcome.

 

[1] – http://docs.aws.amazon.com/lambda/latest/dg/welcome.html

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s