Integrations
You can use the Invoke Lambda Function action with the following integrations:
Filter by label (Content by label) | ||||||
---|---|---|---|---|---|---|
|
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 | ||
---|---|---|
|
{
"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:
Info |
---|
You typically only specify the |
Tip |
---|
You can inject contextual variables into the remote action payload, refer to Entity Variables for details. |
Invoke Lambda Function skeleton
Code Block |
---|
{
|
"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:
Page Properties Report | ||||||
---|---|---|---|---|---|---|
|
Examples
Filter by label (Content by label) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
How-to Articles
Filter by label (Content by label) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Frequently Asked Questions (FAQ)
Include Page | ||||
---|---|---|---|---|
|
Questionslist macro | ||||||||
---|---|---|---|---|---|---|---|---|
|