Integrations
You can use the Start Step Functions Execution action with the following integrations:
Filter by label (Content by label) | ||||||
---|---|---|---|---|---|---|
|
Requirements
The Start Step Functions Execution 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": [ { "Sid": "StepFunctionsServiceActions", "Effect": "Allow", "Action": "states:*", "Resource": "*" }, { "Sid": "StepFunctionsPassRole", "Effect": "Allow", "Action": "iam:PassRole", "Resource": "arn:aws:iam::*:role/service-role/StatesExecutionRole*" } ] } |
Refer to Creating IAM Roles for Use with AWS Step Functions for details on how to create more granular/secure policies.
Configuration
To configure an Start Step Functions Execution action:
Complete the following settings:
Parameters Specify the action parameters according to the following skeleton in JSON format – refer to stepfunctions . start-execution for details:
Info You typically only specify the
stateMachineArn
andinput
parameters, because name must be unique for your AWS account and region and properly defaults to a GUID when absent.Tip You can inject contextual variables into the remote action payload, refer to Entity Variables for details.
Code Block language js title Start Step Functions Execution skeleton linenumbers true { "stateMachineArn": "", "name": "", "input": "" }
Entity Variables
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 | ||||||||
---|---|---|---|---|---|---|---|---|
|