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:
|
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:
Parameters
Specify the action parameters according to the following skeleton in JSON format – refer to lambda . invoke for details:
You typically only specify the |
You can inject contextual variables into the remote action payload, refer to Entity Variables for details. |
Invoke Lambda Function skeleton
{ "FunctionName": "", "Payload": {}, "Qualifier": "", "ClientContext": {} } |
You can inject contextual workflow variables with workflow entities into the remote action payload template – currently available entities are: