AWS CLI for DynamoDB - Time & Space Complexity

Time Complexity: AWS CLI for DynamoDB

O(n)

Understanding Time Complexity

We want to understand how the time needed to run AWS CLI commands for DynamoDB changes as we work with more data.

Specifically, how does the number of operations grow when we scan or query a table with many items?

Scenario Under Consideration

Analyze the time complexity of scanning a DynamoDB table using AWS CLI.

aws dynamodb scan \
  --table-name MusicCollection \
  --filter-expression "Artist = :artist" \
  --expression-attribute-values '{":artist":{"S":"No One You Know"}}'

This command scans the entire MusicCollection table and filters items where the Artist attribute matches "No One You Know".

Identify Repeating Operations

Look at what happens repeatedly during this scan operation.

• Primary operation: Scan API call that reads items page by page.
• How many times: Multiple calls happen internally if the table has many items, because scan reads in chunks (pages).

How Execution Grows With Input

As the number of items in the table grows, the scan operation must read more pages.

Input Size (n)	Approx. API Calls/Operations
10	1 scan call (one page)
100	1-2 scan calls (depending on page size)
1000	Multiple scan calls (many pages)

Pattern observation: The number of scan calls grows roughly in direct proportion to the number of items, because each call reads a limited number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the scan grows linearly with the number of items in the table.

Common Mistake

[X] Wrong: "Scanning a DynamoDB table always takes the same time no matter how many items it has."

[OK] Correct: Scan reads all items page by page, so more items mean more pages and more time.

Interview Connect

Understanding how scan operations scale helps you design efficient data access and shows you know how cloud services behave with growing data.

Self-Check

"What if we changed the scan to a query using a partition key? How would the time complexity change?"

Practice

1. What does the AWS CLI command aws dynamodb list-tables do?

easy

A. It shows all DynamoDB tables in your AWS account and region.

B. It deletes all DynamoDB tables in your AWS account.

C. It creates a new DynamoDB table.

D. It updates the items in a DynamoDB table.

Solution

1. Step 1: Understand the command purpose

   The command aws dynamodb list-tables is designed to list existing tables, not modify or delete them.

2. Step 2: Match command to action

   Listing tables means showing all table names in your current AWS region and account.

3. Final Answer:

   It shows all DynamoDB tables in your AWS account and region. -> Option A

4. Quick Check:

   List tables = Show tables [OK]

Hint: List tables command always shows existing tables [OK]

Common Mistakes:

• Confusing list-tables with delete-table
• Thinking it creates or updates tables
• Assuming it shows table data instead of names

2. Which AWS CLI command syntax correctly adds an item to a DynamoDB table named Books with a primary key ISBN and a title attribute?

easy

A. aws dynamodb add-item --table Books --item '{ISBN: 12345, Title: Cloud Basics}'

B. aws dynamodb put-item --table-name Books --item '{"ISBN": {"S": "12345"}, "Title": {"S": "Cloud Basics"}}'

C. aws dynamodb insert-item --table-name Books --item '{"ISBN": "12345", "Title": "Cloud Basics"}'

D. aws dynamodb put-item --table Books --data '{"ISBN": "12345", "Title": "Cloud Basics"}'

Solution

1. Step 1: Identify correct command and parameters

   The correct command to add an item is put-item with --table-name and --item parameters.

2. Step 2: Check JSON format for item

   The item must be a JSON string with attribute names and types, e.g., {"ISBN": {"S": "12345"}} where "S" means string type.

3. Final Answer:

   aws dynamodb put-item --table-name Books --item '{"ISBN": {"S": "12345"}, "Title": {"S": "Cloud Basics"}}' -> Option B

4. Quick Check:

   Put-item + correct JSON format = aws dynamodb put-item --table-name Books --item '{"ISBN": {"S": "12345"}, "Title": {"S": "Cloud Basics"}}' [OK]

Hint: Use put-item with --item JSON including data types [OK]

Common Mistakes:

• Using wrong command like add-item or insert-item
• Missing data types in JSON attributes
• Using --table instead of --table-name

3. What will be the output of this AWS CLI command?

aws dynamodb get-item --table-name Users --key '{"UserId": {"S": "user123"}}' --projection-expression "Name, Age"

Assuming the table has an item with UserId 'user123', Name 'Alice', Age 30, and Email '[e-mail]'.

medium

A. Returns only the Email attribute.

B. Returns all attributes including Email.

C. Returns an error because projection-expression is invalid.

D. Returns only the Name and Age attributes of the item.

Solution

1. Step 1: Understand get-item with projection-expression

   The --projection-expression limits returned attributes to those listed, here "Name, Age".

2. Step 2: Check expected output

   Since Email is not in projection-expression, it will not be returned. Only Name and Age appear.

3. Final Answer:

   Returns only the Name and Age attributes of the item. -> Option D

4. Quick Check:

   Projection-expression filters attributes = Returns only the Name and Age attributes of the item. [OK]

Hint: Projection-expression returns only listed attributes [OK]

Common Mistakes:

• Assuming all attributes return by default
• Thinking projection-expression causes error
• Confusing projection-expression with filter-expression

4. You run this command but get an error:

aws dynamodb put-item --table-name Products --item '{"ProductId": "123", "Name": "Pen"}'

What is the likely cause of the error?

medium

A. The item JSON is missing data types for attributes.

B. The table name is incorrect.

C. The AWS CLI is not installed.

D. The command should use --update-item instead of --put-item.

Solution

1. Step 1: Check item JSON format requirements

   DynamoDB requires attribute values to specify data types, e.g., {"S": "123"} for string.

2. Step 2: Identify missing data types in JSON

   The command uses plain strings without data types, causing a syntax error.

3. Final Answer:

   The item JSON is missing data types for attributes. -> Option A

4. Quick Check:

   Missing data types in item JSON causes error [OK]

Hint: Always include data types like {"S": "value"} in item JSON [OK]

Common Mistakes:

• Ignoring data type syntax in item JSON
• Assuming --put-item is invalid command
• Not verifying table name correctness

5. You want to create a DynamoDB table named Orders with a primary key OrderId (string) and a sort key OrderDate (string). Which AWS CLI command is correct?

hard

A. aws dynamodb create-table --table-name Orders --attribute-definitions OrderId=S OrderDate=S --key-schema OrderId=HASH OrderDate=RANGE --provisioned-throughput Read=5,Write=5

B. aws dynamodb create-table --table Orders --attributes OrderId=S,OrderDate=S --keys OrderId=HASH,OrderDate=RANGE --throughput 5 5

C. aws dynamodb create-table --table-name Orders --attribute-definitions AttributeName=OrderId,AttributeType=S AttributeName=OrderDate,AttributeType=S --key-schema AttributeName=OrderId,KeyType=HASH AttributeName=OrderDate,KeyType=RANGE --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5

D. aws dynamodb create-table --table-name Orders --attributes OrderId S OrderDate S --key-schema OrderId HASH OrderDate RANGE --capacity 5 5

Solution

1. Step 1: Identify correct command syntax for create-table

   The correct syntax uses --attribute-definitions with AttributeName and AttributeType, and --key-schema with AttributeName and KeyType (HASH for partition key, RANGE for sort key).

2. Step 2: Check provisioned throughput format

   Provisioned throughput requires ReadCapacityUnits and WriteCapacityUnits with numeric values.

3. Final Answer:

   aws dynamodb create-table --table-name Orders --attribute-definitions AttributeName=OrderId,AttributeType=S AttributeName=OrderDate,AttributeType=S --key-schema AttributeName=OrderId,KeyType=HASH AttributeName=OrderDate,KeyType=RANGE --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5 -> Option C

4. Quick Check:

   Create-table syntax with attribute-definitions and key-schema = aws dynamodb create-table --table-name Orders --attribute-definitions AttributeName=OrderId,AttributeType=S AttributeName=OrderDate,AttributeType=S --key-schema AttributeName=OrderId,KeyType=HASH AttributeName=OrderDate,KeyType=RANGE --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5 [OK]

Hint: Use --attribute-definitions and --key-schema with correct keys [OK]

Common Mistakes:

• Using wrong flags like --table or --attributes
• Incorrect key schema format
• Wrong provisioned throughput parameter names