Using the Invoke Lambda Function action

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:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 { "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:

Parameters

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

1 2 3 4 5 6 {     "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:

Examples

How-to Articles

Frequently Asked Questions (FAQ)