Using the Start Step Functions Execution action

Use the Start Step Functions Execution action to process Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions with AWS Step Functions to coordinate multiple AWS services into serverless workflows so you can build and update apps quickly:

Using Step Functions, you can design and run workflows that stitch together services such as AWS Lambda and Amazon ECS into feature-rich applications. Workflows are made up of a series of steps, with the output of one step acting as input into the next. Application development is simpler and more intuitive using Step Functions, because it translates your workflow into a state machine diagram that is easy to understand, easy to explain to others, and easy to change. You can monitor each step of execution as it happens, which means you can identify and fix problems quickly. Step Functions automatically triggers and tracks each step, and retries when there are errors, so your application executes in order and as expected.

On this page:

1 Integrations
2 Requirements
3 Configuration
4 Entity Variables
5 Examples
6 How-to Articles
7 Frequently Asked Questions (FAQ)

Related pages:

Integrations

You can use the Start Step Functions Execution action with the following integrations:

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:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "states:ListStateMachines",
                "states:StartExecution",
                "states:StartSyncExecution"
            ],
            "Effect": "Allow",
            "Resource": "*",
            "Sid": "StepFunctionsStartExecutionAndDiscoverStateMachines"
        },
        {
            "Action": "iam:PassRole",
            "Effect": "Allow",
            "Resource": "arn:aws:iam::*:role/service-role/StatesExecutionRole*"
            "Sid": "StepFunctionsPassRole"
        }
    ]
}

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:

You typically only specify the stateMachineArn and input parameters, because name must be unique for your AWS account and region and properly defaults to a GUID when absent.

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

Start Step Functions Execution skeleton

{
    "stateMachineArn": "",
    "name": "",
    "input": ""
}

Entity Variables

You can inject contextual workflow variables with workflow entities into the remote action payload template – currently available entities are:

Using the Start Step Functions Execution action

Integrations

Requirements

Configuration

Entity Variables

Examples

How-to Articles

Filter by label

Frequently Asked Questions (FAQ)