Step Functions for workflows in AWS - Mini Project: Build & Apply

Step Functions for workflows

📖 Scenario: You are building a simple workflow to automate a package delivery process using AWS Step Functions. The workflow will have steps to check package availability, process payment, and confirm shipment.

🎯 Goal: Create an AWS Step Functions state machine definition in JSON that models the package delivery workflow with three states: CheckAvailability, ProcessPayment, and ConfirmShipment. The workflow should proceed from checking availability to payment processing, then to shipment confirmation, and finally end successfully.

📋 What You'll Learn

Define a state machine with three states named exactly: CheckAvailability, ProcessPayment, and ConfirmShipment.

Each state should be a Task state with a placeholder resource ARN.

The workflow should start at CheckAvailability.

The states should transition in order: CheckAvailability -> ProcessPayment -> ConfirmShipment.

The ConfirmShipment state should be a terminal state with End set to true.

💡 Why This Matters

🌍 Real World

Step Functions help automate complex workflows by connecting multiple AWS services in a reliable sequence.

💼 Career

Understanding Step Functions is essential for cloud engineers and developers building scalable, serverless applications.

1

Create the initial state machine structure

Create a JSON object called stateMachine with a StartAt property set to CheckAvailability and an empty States object.

AWS

{
  "StartAt": "CheckAvailability",
  "States": {
    
  }
}
# Your code here

Hint

Start by defining the StartAt property and an empty States object inside your JSON.

2

Add the CheckAvailability state

Inside the States object, add a state named CheckAvailability with Type set to Task, a placeholder Resource ARN string "arn:aws:lambda:region:account-id:function:CheckAvailability", and Next set to ProcessPayment.

AWS

{
  "StartAt": "CheckAvailability",
  "States": {
    
    // Add CheckAvailability state here
  }
}
# Your code here

Hint

Remember to use the exact state name and set Next to ProcessPayment.

3

Add the ProcessPayment state

Add a state named ProcessPayment inside States with Type set to Task, Resource ARN "arn:aws:lambda:region:account-id:function:ProcessPayment", and Next set to ConfirmShipment.

AWS

{
  "StartAt": "CheckAvailability",
  "States": {
    "CheckAvailability": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:region:account-id:function:CheckAvailability",
      "Next": "ProcessPayment"
    },
    
    // Add ProcessPayment state here
  }
}
# Your code here

Hint

Use the exact state name and set Next to ConfirmShipment.

4

Add the terminal ConfirmShipment state

Add a state named ConfirmShipment inside States with Type set to Task, Resource ARN "arn:aws:lambda:region:account-id:function:ConfirmShipment", and End set to true to mark the workflow completion.

AWS

{
  "StartAt": "CheckAvailability",
  "States": {
    "CheckAvailability": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:region:account-id:function:CheckAvailability",
      "Next": "ProcessPayment"
    },
    "ProcessPayment": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:region:account-id:function:ProcessPayment",
      "Next": "ConfirmShipment"
    },
    
    // Add ConfirmShipment state here
  }
}
# Your code here

Hint

Set End to true to mark this as the final state.

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