Use AWS Lambda in Armory Enterprise

Learn how to use AWS Lambda in a Spinnaker pipeline.

Before you begin

This guide explores a pipeline that tests the various Lambda stages. To deploy the pipeline in your own Armory Enterprise instance, make sure you complete the following:

Configure Armory Enterprise for AWS Lambda
Create a Lambda execution role
Create a Lambda deployment package
Create a Lambda sample payload JSON file
Upload the Lambda deployment package and the Lambda sample payload JSON to an S3 bucket that Armory Enterprise can access
Make sure the SpinnakerManaged role has permission to work with Lambda

AWS Lambda pipeline example

This pipeline is based on the one defined in Enhancing Spinnaker deployment experience of AWS Lambda functions with the Lambda plugin.

Deployment stage

This stage creates a new Lambda function, or updates a Lambda function, and sets various Lambda configurations. If you want a simple update to the code of an existing Lambda function, you should use the Update Code stage instead.

Update Code stage

This stage updates the code of an existing Lambda function.

Invoke stage

This stage executes a Lambda function. The results of this stage are stored in the stage output, which you can access via SpEL with something like the following:

#stage('AWS Lambda Update Invoke').outputs.invokeResultsList

Route stage

This stage routes traffic across various versions of the Lambda function.

Simple strategy

Routes 100% of the traffic to the chosen Target Version of the Lambda function. This example config routes 100% of the traffic to the new Lambda version.

Weighted Deployment strategy

Routes some percentage of the traffic to he chosen Target Version of the Lambda function. This example config routes 40% of the traffic to the new Lambda version.

Blue/Green strategy

Deploys a new version and includes health check configuration to test whether the newly deployed Lambda function is working as expected before routing 100% of traffic to the new version. In case of a health check mismatch, this stage deletes the new version based on the value of the On Fail field.