Using the Invoke Lambda Function action

Use the Invoke Lambda Function action to process Bamboo notifications, JIRA workflow transitions and JIRA Service Desk 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.

On this page:

Related pages:

Injecting contextual entity variables into action payloads
Amazon Web Services
- CLI: lambda . invoke
- API: Lambda >> Invoke
- Tutorial: Using AWS Lambda with Custom User Applications
Using the Publish SNS Message action
Using the Start Step Functions Execution action

Integrations

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

Filter by label

There are no items with the selected labels at this time.

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:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "lambda:GetAlias",
                "lambda:GetFunctionConfiguration",
                "lambda:GetPolicy",
                "lambda:InvokeFunction",
                "lambda:ListAliases",
                "lambda:ListFunctions",
                "lambda:ListVersionsByFunction"
            ],
            "Resource": "*",
            "Effect": "Allow",
            "Sid": "LambdaInvokeFunctionAndDiscoverFunctions"
        }
    ]
}

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:

Complete the following settings:

Entity Variables

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

Using the Invoke Lambda Function action

Integrations

Filter by label

Requirements

Configuration

Entity Variables

Examples

How-to Articles

Frequently Asked Questions (FAQ)