Step Functions with DynamoDB - Mini Project: Build & Apply

Step Functions with DynamoDB

📖 Scenario: You are building a simple order tracking system for a small online store. The system uses AWS Step Functions to manage the order process and DynamoDB to store order data.Each order has an OrderId, CustomerName, Status, and TotalAmount.

🎯 Goal: Create a DynamoDB table called Orders with the specified attributes. Then, configure a Step Function state to insert a new order into the Orders table. Finally, update the order status using Step Functions.

📋 What You'll Learn

Create a DynamoDB table named Orders with OrderId as the primary key.

Add an initial order item with OrderId '1001', CustomerName 'Alice', Status 'Pending', and TotalAmount 250.

Create a Step Function task state to insert the order into the Orders table.

Create a Step Function task state to update the Status of the order to 'Shipped'.

💡 Why This Matters

🌍 Real World

Managing order workflows in e-commerce platforms using AWS Step Functions and DynamoDB for reliable state management and data storage.

💼 Career

Understanding how to integrate AWS Step Functions with DynamoDB is valuable for cloud engineers and developers working on serverless applications and workflow automation.

1

Create the DynamoDB table and initial order item

Write the AWS CLI command to create a DynamoDB table named Orders with OrderId as the partition key of type string. Then, write the AWS CLI command to put an item into the Orders table with OrderId '1001', CustomerName 'Alice', Status 'Pending', and TotalAmount 250.

DynamoDB

# Your AWS CLI commands here

Hint

Use aws dynamodb create-table with --attribute-definitions and --key-schema. Use aws dynamodb put-item with the JSON item.

2

Define the Step Function task to insert an order

Write a JSON snippet defining a Step Function task state named InsertOrder that uses the arn:aws:states:::dynamodb:putItem resource to insert an order into the Orders table. The task should use OrderId, CustomerName, Status, and TotalAmount from the input. Use TableName as Orders.

DynamoDB

aws dynamodb create-table --table-name Orders --attribute-definitions AttributeName=OrderId,AttributeType=S --key-schema AttributeName=OrderId,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5
aws dynamodb put-item --table-name Orders --item '{"OrderId": {"S": "1001"}, "CustomerName": {"S": "Alice"}, "Status": {"S": "Pending"}, "TotalAmount": {"N": "250"}}'

# Define the InsertOrder task state JSON below

Hint

Use "Resource": "arn:aws:states:::dynamodb:putItem" and "Parameters" with TableName and Item. Use .$ to reference input fields.

3

Define the Step Function task to update order status

Write a JSON snippet defining a Step Function task state named UpdateOrderStatus that uses the arn:aws:states:::dynamodb:updateItem resource to update the Status attribute of an order in the Orders table. Use OrderId from the input as the key. Set the Status attribute to 'Shipped'.

DynamoDB

aws dynamodb create-table --table-name Orders --attribute-definitions AttributeName=OrderId,AttributeType=S --key-schema AttributeName=OrderId,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5
aws dynamodb put-item --table-name Orders --item '{"OrderId": {"S": "1001"}, "CustomerName": {"S": "Alice"}, "Status": {"S": "Pending"}, "TotalAmount": {"N": "250"}}'

"InsertOrder": {
  "Type": "Task",
  "Resource": "arn:aws:states:::dynamodb:putItem",
  "Parameters": {
    "TableName": "Orders",
    "Item": {
      "OrderId": {"S.$": "$.OrderId"},
      "CustomerName": {"S.$": "$.CustomerName"},
      "Status": {"S.$": "$.Status"},
      "TotalAmount": {"N.$": "$.TotalAmount"}
    }
  },
  "End": true
}

# Define the UpdateOrderStatus task state JSON below

Hint

Use arn:aws:states:::dynamodb:updateItem with UpdateExpression to set Status. Use ExpressionAttributeNames and ExpressionAttributeValues to specify the new status.

4

Complete the Step Function definition with both tasks

Combine the InsertOrder and UpdateOrderStatus task states into a Step Function state machine JSON. The state machine should start with InsertOrder and then transition to UpdateOrderStatus. Mark UpdateOrderStatus as the end state.

DynamoDB

aws dynamodb create-table --table-name Orders --attribute-definitions AttributeName=OrderId,AttributeType=S --key-schema AttributeName=OrderId,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5
aws dynamodb put-item --table-name Orders --item '{"OrderId": {"S": "1001"}, "CustomerName": {"S": "Alice"}, "Status": {"S": "Pending"}, "TotalAmount": {"N": "250"}}'

# Combine InsertOrder and UpdateOrderStatus states into a state machine JSON below

Hint

Use "StartAt" to set the first state. Use "Next" in InsertOrder to go to UpdateOrderStatus. Mark UpdateOrderStatus with "End": true.

Practice

1. What is the main purpose of using AWS Step Functions with DynamoDB?

easy

A. To automate workflows that involve storing and retrieving data step by step

B. To create visual dashboards for DynamoDB data

C. To replace DynamoDB with a different database

D. To manually update DynamoDB tables without code

Solution

1. Step 1: Understand Step Functions role

   Step Functions help run tasks in a specific order automatically.

2. Step 2: Connect with DynamoDB usage

   DynamoDB stores data quickly and safely, and Step Functions can automate tasks that read or write this data.

3. Final Answer:

   To automate workflows that involve storing and retrieving data step by step -> Option A

4. Quick Check:

   Step Functions + DynamoDB = automated data workflows [OK]

Hint: Step Functions automate tasks; DynamoDB stores data fast [OK]

Common Mistakes:

• Thinking Step Functions create dashboards
• Believing Step Functions replace DynamoDB
• Assuming manual updates are the main use

2. Which of the following is the correct Resource ARN for a DynamoDB operation (e.g., PutItem) in a Step Functions state using Amazon States Language (ASL)?

easy

A. "Resource": "arn:aws:s3:::TableName"

B. "Resource": "dynamodb://TableName"

C. "Resource": "arn:aws:states:::dynamodb:putItem"

D. "Resource": "lambda:TableName"

Solution

1. Step 1: Identify correct ARN format for DynamoDB

   Step Functions uses optimized integrations for DynamoDB with ARNs starting with "arn:aws:states:::dynamodb:" followed by the action like putItem.

2. Step 2: Check options for correct ARN

   "Resource": "arn:aws:states:::dynamodb:putItem" matches the correct optimized integration format; others reference wrong services or formats.

3. Final Answer:

   "Resource": "arn:aws:states:::dynamodb:putItem" -> Option C

4. Quick Check:

   Step Functions DynamoDB ARN = "arn:aws:states:::dynamodb:putItem" [OK]

Hint: Step Functions DynamoDB ARNs: arn:aws:states:::dynamodb:[action] [OK]

Common Mistakes:

• Using S3 or Lambda ARNs for DynamoDB
• Using URL-like syntax instead of ARN
• Missing optimized integration format

3. Given this Step Functions task state calling DynamoDB PutItem:

{
  "Type": "Task",
  "Resource": "arn:aws:states:::dynamodb:putItem",
  "Parameters": {
    "TableName": "Users",
    "Item": {
      "UserId": {"S": "123"},
      "Name": {"S": "Alice"}
    }
  },
  "End": true
}

What will happen when this state runs?

medium

A. It will add a new item with UserId 123 and Name Alice to the Users table

B. It will delete the item with UserId 123 from the Users table

C. It will update the Name of UserId 123 only if it exists

D. It will cause a syntax error and fail

Solution

1. Step 1: Understand the PutItem action

   PutItem adds a new item or replaces an existing item in DynamoDB with the given attributes.

2. Step 2: Analyze the Parameters

   The Parameters specify the table "Users" and an item with UserId "123" and Name "Alice" to be added.

3. Final Answer:

   It will add a new item with UserId 123 and Name Alice to the Users table -> Option A

4. Quick Check:

   PutItem adds or replaces item = It will add a new item with UserId 123 and Name Alice to the Users table [OK]

Hint: PutItem adds or replaces items in DynamoDB [OK]

Common Mistakes:

• Confusing PutItem with DeleteItem
• Thinking PutItem only updates existing items
• Assuming syntax error without checking JSON

4. You have this Step Functions state to get an item from DynamoDB:

{
  "Type": "Task",
  "Resource": "arn:aws:states:::dynamodb:getItem",
  "Parameters": {
    "TableName": "Orders",
    "Key": {
      "OrderId": {}
    }
  },
  "End": true
}

What is the problem with this state?

medium

A. TableName should be lowercase

B. The Resource ARN is incorrect for getItem

C. End cannot be true in a Task state

D. The Key value for OrderId is empty, causing a runtime error

Solution

1. Step 1: Check the Key parameter

   The Key must have a valid AttributeValue (with type like S/N); here OrderId is an empty object {}, which is invalid for DynamoDB keys.

2. Step 2: Validate other parameters

   Resource ARN is correct, TableName case is fine, and End:true is allowed in Task states.

3. Final Answer:

   The Key value for OrderId is empty, causing a runtime error -> Option D

4. Quick Check:

   Empty key value causes error = The Key value for OrderId is empty, causing a runtime error [OK]

Hint: DynamoDB keys must have non-empty values [OK]

Common Mistakes:

• Thinking ARN is wrong
• Believing TableName must be lowercase
• Assuming End:true is invalid

5. You want to create a Step Functions workflow that first writes a new user to DynamoDB, then reads the user back to confirm. Which sequence of states correctly achieves this?

hard

A. First a Task state with arn:aws:states:::dynamodb:getItem, then a Task state with arn:aws:states:::dynamodb:putItem

B. First a Task state with Resource arn:aws:states:::dynamodb:putItem, then a Task state with arn:aws:states:::dynamodb:getItem

C. A single Task state with arn:aws:states:::dynamodb:updateItem

D. Two parallel states both using arn:aws:states:::dynamodb:putItem

Solution

1. Step 1: Determine the write then read order

   You must first add the user with putItem, then read it with getItem to confirm.

2. Step 2: Check the options for correct sequence

   First a Task state with Resource arn:aws:states:::dynamodb:putItem, then a Task state with arn:aws:states:::dynamodb:getItem correctly sequences putItem followed by getItem; others have wrong order or wrong actions.

3. Final Answer:

   First a Task state with Resource arn:aws:states:::dynamodb:putItem, then a Task state with arn:aws:states:::dynamodb:getItem -> Option B

4. Quick Check:

   Write then read = First a Task state with Resource arn:aws:states:::dynamodb:putItem, then a Task state with arn:aws:states:::dynamodb:getItem [OK]

Hint: Write with putItem before reading with getItem [OK]

Common Mistakes:

• Reading before writing
• Using updateItem instead of putItem
• Running writes in parallel without read