Versions Compared

Old Version 3

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

compared with

New Version 4

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added requirements section.

Excerpt
Div
stylefloat:left; padding:0.5em 1em

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:

Div
styleclear:both

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.

Panel
borderColor#bbb
bgColor#eeeeee

On this page:

Table of Contents
maxLevel2
exclude(Popular.*|Recent.*)

Panel
borderColor#bbb
bgColor#eeeeee

Related pages:

Integrations

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

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
cqllabel = "integration" and label in ("bamboo","bitbucket","confluence","jira") and space = currentSpace()

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:

Code Block
languagejs
linenumberstrue
collapsetrue
{
    "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"
        }
    ]
}

(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:

    Info

    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).

    Tip

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

    Code Block
    languagejs
    titleInvoke Lambda Function skeleton
    linenumberstrue
    {
    "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:
Filter by label (Content by label)
showSpacefalse
excerptTypesimple
cqllabel = "entity" and label = "context"

Examples

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
sorttitle
excerptTypesimple
cqllabel = "example" and label = "parameters" and label = "invoke-lambda-function"

How-to Articles

Filter by label (Content by label)
max8
showSpacefalse
sorttitle
excerptTypesimple
cqllabel in ("action","lambda","function") and label in ("kb-how-to-article","kb-troubleshooting-article") and label = "automation-with-aws"

Frequently Asked Questions (FAQ)

Questionslist macro
filterpopular
asktrue
limit8
topicautomation-with-aws,action,lambda,function