Step Functions with DynamoDB - Step-by-Step Execution

Concept Flow - Step Functions with DynamoDB

Start Step Function

↓

Invoke DynamoDB Operation

↓

Check Operation Result

↓

Next Step

↓

End

The Step Function starts, calls a DynamoDB operation, checks the result, then either proceeds to the next step on success or handles errors with retry or termination.

Execution Sample

DynamoDB

StartExecution -> PutItem in DynamoDB -> Check Result -> Success? -> Next Step or Retry

This flow shows a Step Function calling DynamoDB to put an item, then deciding next steps based on success or failure.

Execution Table

Step	Action	DynamoDB Operation	Result	Next Step
1	Start Step Function	None	Started	Invoke PutItem
2	Invoke DynamoDB PutItem	PutItem	Success	Proceed to Next Step
3	Check Result	PutItem	Success	Next Step
4	Execute Next Step	None	Completed	End Execution
5	End	None	Execution Finished	Stop

💡 Execution stops after successful PutItem and completion of next step.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
ExecutionStatus	Not started	Running	Success	Completed
DynamoDBResponse	None	{"PutItem": "Success"}	{"PutItem": "Success"}	{"PutItem": "Success"}

Key Moments - 2 Insights

Why does the Step Function check the DynamoDB operation result before proceeding?

Because the execution_table shows at Step 3 the result is checked to decide if the flow should continue or handle errors. This ensures the next step only runs if DynamoDB succeeded.

What happens if the DynamoDB PutItem operation fails?

Though not shown in this trace, the concept_flow diagram shows that on failure, the Step Function would handle the error, possibly retrying or ending execution.

Visual Quiz - 3 Questions

Look at the execution_table, what is the DynamoDB operation result at Step 2?

A Failure

B Pending

C Success

D Not started

💡 Hint

Check the 'Result' column at Step 2 in the execution_table.

At which step does the Step Function decide to proceed to the next step after DynamoDB operation?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Next Step' column and see where the decision based on result is made.

If the PutItem operation failed, what would the Step Function do according to the concept_flow?

A Handle error and retry or end

B Proceed to next step anyway

C Ignore and stop execution

D Restart the entire Step Function

💡 Hint

Refer to the concept_flow diagram branch for failure after checking operation result.

Concept Snapshot

Step Functions with DynamoDB:
- Start Step Function
- Call DynamoDB operation (e.g., PutItem)
- Check operation result
- On success, proceed to next step
- On failure, handle error (retry or end)
- End execution after steps complete

Full Transcript

This visual execution shows how a Step Function interacts with DynamoDB. It starts execution, calls a DynamoDB PutItem operation, then checks the result. If the operation succeeds, it proceeds to the next step and eventually ends. If the operation fails, the Step Function handles the error by retrying or ending. Variables like ExecutionStatus and DynamoDBResponse track the state. This flow ensures reliable database operations within automated workflows.

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