AWS Step functions and Lambda for Serverless Orchestration Workflows

Sanket Bengali
Jun 8 · 4 min read
Source AWS Step functions


Step Functions have State Machines i.e. Workflows where each step can execute a Lambda function.

Workflows are made up of a series of steps, with the output of one step acting as input into the next.

It allows Looping, branching, wait etc. (Task Choice Wait Parallel) to design custom workflows to implement any Orchestration use-case.

Step functions can be used to eliminate Lambda’s time limitation by having workflows of sequential function calls.

With the combination of Step functions and Lambda, any custom orchestration use-case can be achieved.

Sky is the limit.


Using Step functions as a Backup solution

While AWS Step functions can be used to achieve any complex Orchestration use-case, one good use-case is when application backup (for large-scale, distributed systems that uses multiple AWS services) needs to be taken using custom scripts (Lambda functions) instead of using native Backup services.


AWS Step functions screenshots

Step functions
Workflow details
Workflow execution
Workflow in “Running” state
Workflow successful execution
Execution event history
Workflow execution inputs and outputs
Workflow failed execution

AWS Lambda functions screenshots

Lambda functions
Lambda function details
Lambda function code
Environment variables and tags
Execution role and basic settings (memory, timeout (max. = 15 mins))
VPC network and additional options (debugging, error handling, concurrency)

The Startup

Medium's largest active publication, followed by +469K people. Follow to join our community.

Sanket Bengali

Written by

The Startup

Medium's largest active publication, followed by +469K people. Follow to join our community.