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.


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


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.


To configure an Invoke Lambda Function action:

Complete the following settings:


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

You typically only specify the FunctionName and Payload parameters, and not all parameters documented for lambda . invoke are applicable here (invocation-type and log-type are not meaningful, and outfile is not supported).

You can inject contextual variables into the remote action payload, refer to Entity Variables for details.

Invoke Lambda Function skeleton

{     "FunctionName": "",     "Payload": {},     "Qualifier": "",     "ClientContext": {} }

Entity Variables

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


How-to Articles

Filter by label

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

Frequently Asked Questions (FAQ)

Atlassian®, Atlassian Bamboo®, Bitbucket®, Atlassian Crowd®, Confluence®, Jira®, Jira Service Management™, Opsgenie®, and Statuspage™ are registered trademarks of Atlassian.
Amazon Web Services™, AWS™ and the “Powered by Amazon Web Services” logo are trademarks of, Inc. or its affiliates in the United States and/or other countries.

Utoolity® is a registered trademark of Utoolity GmbH.
© 2024 Utoolity GmbH. All rights reserved.