Using the Invoke Lambda Function action

Use the Invoke Lambda Function action to process Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions with AWS Lambda, which lets you run code without provisioning or managing servers:

You pay only for the compute time you consume - there is no charge when your code is not running. With Lambda, you can run code for virtually any type of application or backend service - all with zero administration. Just upload your code and Lambda takes care of everything required to run and scale your code with high availability. You can set up your code to automatically trigger from other AWS services or call it directly from any web or mobile app.

Integrations

You can use the Invoke Lambda Function action with the following integrations:

Requirements

The Invoke Lambda Function action requires sufficient IAM permissions - an adequate IAM policy similar to the one provisioned by the Automation with AWS (Core) CloudFormation template might look as follows:

(lightbulb) Refer to Overview of Managing Access Permissions to Your AWS Lambda Resources for details on how to create more granular/secure policies.

Configuration

To configure an Invoke Lambda Function action:

  1. Complete the following settings:

    Parameters

    Specify the action parameters according to the following skeleton in JSON format – refer to lambda . invoke for details:

Entity Variables

You can inject contextual workflow variables with workflow entities into the remote action payload template – currently available entities are:

Examples

How-to Articles

Frequently Asked Questions (FAQ)