AWS Step Functions Adds Support for Nested Workflows

Posted on: Aug 12, 2019

AWS Step Functions now allows you to orchestrate more complex processes by composing modular, reusable workflows. 

Step Functions lets you coordinate multiple AWS services in fully-managed workflows so you can build and update apps quickly. As organizations use workflows more extensively, their workflows become complicated to build, test, and change. Common workflow processes are often repeated in multiple places. Large workflow executions are also harder to troubleshoot when things go wrong.  

By nesting your Step Functions workflows, you can build larger, more complex workflows out of smaller, simpler workflows. When your workflows have recurring processes such as human review and approval or resource provisioning in accounts, you can create a library of modular, reusable building blocks for faster development. Step Functions allows you to swap and reorganize workflow modules without customizing code. This allows you to assemble new workflows out of your existing workflows in minutes. You can separate high-level workflow steps from low-level workflow steps for easier monitoring and spotting error sources in seconds. In the Step Functions console, you can switch between visualizations of different workflow levels with a single click. 

You launch a nested workflow execution from a single workflow step. You can configure your workflow to start a nested workflow using code snippets in the console. Alternatively, you can try a Sample Project in the console to deploy a complete example. 

There is no additional charge for starting a nested workflow. Nested workflows are billed the same as all Step Functions workflows. For more information, see AWS Step Functions pricing. Nested workflows are available in all AWS public regions where Step Functions is available. For a complete list of regions where AWS Step Functions is offered, see AWS Regions.  

To learn more about Step Functions, read the AWS Step Functions Developer Guide. To learn more about composing nested workflows, read the section on AWS Service Integrations