Step Functions for workflows in AWS - Commands & Configuration

Introduction

Sometimes you want to run tasks one after another or in a specific order automatically. AWS Step Functions help you create these task sequences so your app can do many things step-by-step without you doing it manually.

When you want to automate a process that has multiple steps, like processing an order and then sending a confirmation email.

When you need to run tasks in order and handle errors if something goes wrong.

When you want to connect different AWS services to work together smoothly.

When you want to see the progress of a multi-step job in one place.

When you want to retry a task automatically if it fails.

Config File - state_machine.json

state_machine.json

{
  "Comment": "A simple AWS Step Functions state machine example",
  "StartAt": "HelloWorld",
  "States": {
    "HelloWorld": {
      "Type": "Pass",
      "Result": "Hello, Step Functions!",
      "End": true
    }
  }
}

This JSON file defines a simple Step Functions workflow.

StartAt tells which step to start with.

States lists all steps. Here, there is one step called HelloWorld.

Type: Pass means this step just passes data through without doing work.

Result is the output of this step.

End: true means this is the last step.

Commands

This command creates a new Step Functions state machine named MyStateMachine using the JSON definition file. The role ARN gives permission to run the workflow.

Terminal

aws stepfunctions create-state-machine --name MyStateMachine --role-arn arn:aws:iam::123456789012:role/service-role/StepFunctions-MyRole --definition file://state_machine.json --region us-east-1

Expected Output

{

    "stateMachineArn": "arn:aws:states:us-east-1:123456789012:stateMachine:MyStateMachine"

}

→

--name - Sets the name of the state machine.

→

--role-arn - Specifies the IAM role that Step Functions uses to run the workflow.

→

--definition - Points to the JSON file that defines the workflow steps.

This command starts running the workflow named MyStateMachine. The execution is given a unique name 'execution1' to track it.

Terminal

aws stepfunctions start-execution --state-machine-arn arn:aws:states:us-east-1:123456789012:stateMachine:MyStateMachine --name execution1 --region us-east-1

Expected Output

{

    "executionArn": "arn:aws:states:us-east-1:123456789012:execution:MyStateMachine:execution1",

    "startDate": 1686000000.0

}

→

--state-machine-arn - Specifies which state machine to run.

→

--name - Gives a unique name to this run of the workflow.

This command checks the status and details of the running or finished workflow execution named 'execution1'.

Terminal

aws stepfunctions describe-execution --execution-arn arn:aws:states:us-east-1:123456789012:execution:MyStateMachine:execution1 --region us-east-1

Expected Output

{

    "executionArn": "arn:aws:states:us-east-1:123456789012:execution:MyStateMachine:execution1",

    "stateMachineArn": "arn:aws:states:us-east-1:123456789012:stateMachine:MyStateMachine",

    "status": "SUCCEEDED",

    "startDate": 1686000000.0,

    "stopDate": 1686000001.0,

    "output": "\"Hello, Step Functions!\""

}

→

--execution-arn - Specifies which execution to describe.

Key Concept

If you remember nothing else from this pattern, remember: Step Functions let you automate and track multi-step tasks easily by defining each step and how they connect.

Common Mistakes

Using an IAM role ARN that does not have permission for Step Functions.

The state machine creation or execution will fail due to lack of permissions.

Create or use an IAM role with the AWS managed policy 'AWSStepFunctionsFullAccess' or a custom role with needed permissions.

Forgetting to use 'file://' prefix when specifying the JSON definition file.

The CLI will treat the argument as a string instead of a file path and fail to load the workflow definition.

Always use 'file://state_machine.json' to tell AWS CLI to read the file content.

Starting an execution with a name that already exists.

Step Functions requires unique execution names; duplicate names cause errors.

Use a unique name for each execution or omit the --name flag to let AWS generate one.

Summary

Create a state machine with a JSON file that defines the workflow steps.

Start an execution of the state machine to run the workflow.

Check the execution status and output to see the results.

Practice

1. What is the main purpose of AWS Step Functions in a workflow?

easy

A. To monitor network traffic between AWS services

B. To coordinate and manage the sequence of tasks in a workflow

C. To provide a user interface for AWS services

D. To store large amounts of data for applications

Solution

1. Step 1: Understand the role of Step Functions

   AWS Step Functions help organize and control the order of tasks in a workflow, making sure each step runs in sequence or parallel as needed.

2. Step 2: Compare with other AWS services

   Other options describe storage, UI, or monitoring, which are not the main functions of Step Functions.

3. Final Answer:

   To coordinate and manage the sequence of tasks in a workflow -> Option B

4. Quick Check:

   Step Functions = task coordination [OK]

Hint: Step Functions organize tasks step-by-step [OK]

Common Mistakes:

• Confusing Step Functions with storage services
• Thinking Step Functions provide UI
• Assuming Step Functions monitor network traffic

2. Which JSON field is required to define a task state in an AWS Step Functions state machine?

easy

A. "Timeout" specifying the maximum execution time

B. "Retry" specifying the retry policy

C. "InputPath" specifying the input data format

D. "Resource" specifying the ARN of the task to run

Solution

1. Step 1: Identify the key field for task execution

   The "Resource" field is mandatory in a task state to specify which AWS service or Lambda function to invoke.

2. Step 2: Understand other fields

   "Timeout", "InputPath", and "Retry" are optional fields that control behavior but are not required to define a task.

3. Final Answer:

   "Resource" specifying the ARN of the task to run -> Option D

4. Quick Check:

   Task state needs "Resource" [OK]

Hint: "Resource" points to the task to run [OK]

Common Mistakes:

• Confusing optional fields with required ones
• Using "Timeout" as a required field
• Forgetting to specify the task ARN

3. Given this Step Functions snippet, what is the next state after TaskA completes successfully?

{
  "StartAt": "TaskA",
  "States": {
    "TaskA": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:region:123456789012:function:FunctionA",
      "Next": "TaskB"
    },
    "TaskB": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:region:123456789012:function:FunctionB",
      "End": true
    }
  }
}

medium

A. TaskB

B. TaskA

C. End state

D. No next state defined

Solution

1. Step 1: Read the "Next" field of TaskA

   The JSON shows "Next": "TaskB" for TaskA, meaning after TaskA finishes, the workflow moves to TaskB.

2. Step 2: Confirm TaskB is defined

   TaskB is defined and marked with "End": true, so it is the final step after TaskA.

3. Final Answer:

   TaskB -> Option A

4. Quick Check:

   TaskA's "Next" = TaskB [OK]

Hint: Check the "Next" field for the following state [OK]

Common Mistakes:

• Assuming TaskA loops to itself
• Thinking workflow ends after TaskA
• Ignoring the "Next" field

4. You have this Step Functions state definition:

{
  "Type": "Task",
  "Resource": "arn:aws:lambda:region:123456789012:function:MyFunction",
  "Next": "NextState"
}

What is missing that could cause a failure if the Lambda function errors?

medium

A. "Catch" block to handle errors

B. "TimeoutSeconds" field to limit execution time

C. "ResultPath" to store output

D. "StartAt" field to define the first state

Solution

1. Step 1: Identify error handling in Step Functions

   Without a "Catch" block, errors from the Lambda function cause the workflow to fail immediately.

2. Step 2: Understand other fields

   "TimeoutSeconds" limits time but is optional; "ResultPath" controls output storage; "StartAt" is for the state machine root, not individual states.

3. Final Answer:

   "Catch" block to handle errors -> Option A

4. Quick Check:

   Error handling needs "Catch" [OK]

Hint: Add "Catch" to handle task errors safely [OK]

Common Mistakes:

• Confusing "TimeoutSeconds" with error handling
• Omitting "Catch" causes workflow failure on error
• Thinking "StartAt" is needed inside a task

5. You want to build a workflow that runs two Lambda functions in parallel and then proceeds only when both finish successfully. Which Step Functions state type should you use?

hard

A. Map state

B. Choice state

C. Parallel state

D. Pass state

Solution

1. Step 1: Understand the requirement for parallel execution

   Running two Lambda functions at the same time and waiting for both to finish requires a "Parallel" state.

2. Step 2: Review other state types

   "Choice" is for branching decisions, "Map" is for iterating over items, and "Pass" passes data without work.

3. Final Answer:

   Parallel state -> Option C

4. Quick Check:

   Parallel state runs tasks simultaneously [OK]

Hint: Use Parallel state to run tasks together [OK]

Common Mistakes:

• Using Choice state for parallelism
• Confusing Map state with parallel execution
• Thinking Pass state runs tasks