Using the Start Step Functions Execution action
The following macros are not currently supported in the header:
  • unmigrated-wiki-markup

Documentation for Automation with AWS AWS 1.1 – other releases are available in the Automation with AWS Documentation Directory.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Using the Start Step Functions Execution action

Use the Start Step Functions Execution action to process Bamboo notifications, JIRA workflow transitions and JIRA Service Desk automation rule executions with AWS Step Functions to coordinate the components of distributed applications and microservices using visual workflows:

Building applications from individual components that each perform a discrete function lets you scale and change applications quickly. Step Functions is a reliable way to coordinate components and step through the functions of your application. Step Functions provides a graphical console to arrange and visualize the components of your application as a series of steps. This makes it simple to build and run multi-step applications. Step Functions automatically triggers and tracks each step, and retries when there are errors, so your application executes in order and as expected. Step Functions logs the state of each step, so when things do go wrong, you can diagnose and debug problems quickly. You can change and add steps without even writing code, so you can easily evolve your application and innovate faster.

Integrations

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

Filter by label

There are no items with the selected labels at this time.

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": [ { "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:

  1. Complete the following settings:

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)

Atlassian®, Atlassian Bamboo®, Bitbucket®, Atlassian Crowd®, Confluence®, Jira®, Jira Service Management™, Opsgenie®, and Statuspage™ are registered trademarks of Atlassian.
Amazon Web Services™, AWS™ and the “Powered by Amazon Web Services” logo are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.

Utoolity® is a registered trademark of Utoolity GmbH.
© 2025 Utoolity GmbH. All rights reserved.