Bird
Raised Fist0
AWScloud~5 mins

Creating a DynamoDB table in AWS - Step-by-Step CLI Walkthrough

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Introduction
Sometimes you need a fast and simple way to store data that your app can quickly read and write. DynamoDB is a service that lets you create a table to store this data without worrying about managing servers.
When you want to store user profiles for a web app with quick access.
When you need to save session data for a mobile app that many users access.
When you want to keep track of orders in an online store with fast lookups.
When you need a database that automatically scales with your app's traffic.
When you want a simple key-value store without setting up a traditional database.
Config File - create-table.json
create-table.json
{
  "TableName": "example-table",
  "AttributeDefinitions": [
    {
      "AttributeName": "UserId",
      "AttributeType": "S"
    }
  ],
  "KeySchema": [
    {
      "AttributeName": "UserId",
      "KeyType": "HASH"
    }
  ],
  "ProvisionedThroughput": {
    "ReadCapacityUnits": 5,
    "WriteCapacityUnits": 5
  }
}

TableName: The name of your DynamoDB table.

AttributeDefinitions: Defines the attributes used as keys, here 'UserId' as a string.

KeySchema: Sets 'UserId' as the primary key (HASH key).

ProvisionedThroughput: Sets how much read and write capacity the table has, here 5 units each.

Commands
This command creates a DynamoDB table using the settings defined in the JSON file.
Terminal
aws dynamodb create-table --cli-input-json file://create-table.json
Expected OutputExpected
{ "TableDescription": { "AttributeDefinitions": [ { "AttributeName": "UserId", "AttributeType": "S" } ], "TableName": "example-table", "KeySchema": [ { "AttributeName": "UserId", "KeyType": "HASH" } ], "TableStatus": "CREATING", "CreationDateTime": "2024-06-01T12:00:00.000Z", "ProvisionedThroughput": { "ReadCapacityUnits": 5, "WriteCapacityUnits": 5, "NumberOfDecreasesToday": 0 }, "TableSizeBytes": 0, "ItemCount": 0, "TableArn": "arn:aws:dynamodb:us-east-1:123456789012:table/example-table" } }
→
--cli-input-json - Specifies the JSON file with the table configuration.
This command checks the status and details of the table to confirm it was created successfully.
Terminal
aws dynamodb describe-table --table-name example-table
Expected OutputExpected
{ "Table": { "AttributeDefinitions": [ { "AttributeName": "UserId", "AttributeType": "S" } ], "TableName": "example-table", "KeySchema": [ { "AttributeName": "UserId", "KeyType": "HASH" } ], "TableStatus": "ACTIVE", "CreationDateTime": "2024-06-01T12:00:00.000Z", "ProvisionedThroughput": { "ReadCapacityUnits": 5, "WriteCapacityUnits": 5, "NumberOfDecreasesToday": 0 }, "TableSizeBytes": 0, "ItemCount": 0, "TableArn": "arn:aws:dynamodb:us-east-1:123456789012:table/example-table" } }
→
--table-name - Specifies the name of the table to describe.
Key Concept

If you remember nothing else from this pattern, remember: you create a DynamoDB table by defining its keys and capacity in a JSON file and then running a create command with that file.

Common Mistakes
Using an attribute in KeySchema that is not defined in AttributeDefinitions.
DynamoDB requires all key attributes to be defined first; otherwise, the table creation fails.
Make sure every attribute used as a key is listed in AttributeDefinitions with its type.
Not waiting for the table status to become ACTIVE before using it.
Trying to use the table while it is still CREATING will cause errors.
Use the describe-table command to check the status and wait until it shows ACTIVE.
Summary
Create a JSON file that defines the table name, keys, and capacity.
Run the AWS CLI create-table command with the JSON file to make the table.
Check the table status with describe-table to ensure it is ready to use.

Practice

(1/5)
1. What is the main purpose of the primary key when creating a DynamoDB table?
easy
A. To define the table's read capacity
B. To store the table's name
C. To specify the AWS region
D. To uniquely identify each item in the table

Solution

  1. Step 1: Understand the role of the primary key

    The primary key uniquely identifies each item in a DynamoDB table, ensuring no duplicates.

  2. Step 2: Differentiate from other table properties

    Table name, capacity, and region do not serve as unique identifiers for items.

  3. Final Answer:

    To uniquely identify each item in the table -> Option D

  4. Quick Check:

    Primary key = unique item ID [OK]
Hint: Primary key means unique ID for each item [OK]
Common Mistakes:
  • Confusing primary key with table name
  • Thinking capacity defines uniqueness
  • Mixing region with key attributes
2. Which AWS CLI command correctly creates a DynamoDB table named Users with a primary key UserId of type string?
easy
A. aws dynamodb create-table --table-name Users --attribute-definitions AttributeName=UserId,AttributeType=S --key-schema AttributeName=UserId,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5
B. aws dynamodb create-table --name Users --key UserId --type String
C. aws dynamodb make-table --table Users --key UserId --type S
D. aws dynamodb create-table --table Users --attribute UserId String --key UserId HASH

Solution

  1. Step 1: Identify correct AWS CLI syntax for creating a table

    The correct command uses create-table with --table-name, --attribute-definitions, --key-schema, and --provisioned-throughput.

  2. Step 2: Verify attribute and key schema details

    AttributeName=UserId with AttributeType=S (string) and KeyType=HASH for primary key is correct.

  3. Final Answer:

    aws dynamodb create-table --table-name Users --attribute-definitions AttributeName=UserId,AttributeType=S --key-schema AttributeName=UserId,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5 -> Option A

  4. Quick Check:

    Correct CLI syntax = aws dynamodb create-table --table-name Users --attribute-definitions AttributeName=UserId,AttributeType=S --key-schema AttributeName=UserId,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5 [OK]
Hint: Use --attribute-definitions and --key-schema for keys [OK]
Common Mistakes:
  • Using wrong command like make-table
  • Missing provisioned throughput
  • Incorrect flags like --name instead of --table-name
3. Given this AWS CLI command:
aws dynamodb create-table --table-name Products --attribute-definitions AttributeName=ProductId,AttributeType=S AttributeName=Category,AttributeType=S --key-schema AttributeName=ProductId,KeyType=HASH AttributeName=Category,KeyType=RANGE --provisioned-throughput ReadCapacityUnits=10,WriteCapacityUnits=5

What is the primary key type of the Products table?
medium
A. No primary key defined
B. Simple primary key with only a HASH key
C. Composite primary key with HASH and RANGE keys
D. Primary key with only a RANGE key

Solution

  1. Step 1: Analyze the key schema in the command

    The command defines two keys: ProductId as HASH and Category as RANGE.

  2. Step 2: Understand primary key types in DynamoDB

    A primary key with both HASH and RANGE keys is called a composite primary key.

  3. Final Answer:

    Composite primary key with HASH and RANGE keys -> Option C

  4. Quick Check:

    HASH + RANGE = composite key [OK]
Hint: HASH + RANGE keys mean composite primary key [OK]
Common Mistakes:
  • Thinking two attributes mean no key
  • Confusing RANGE key as standalone primary key
  • Ignoring key-schema details
4. You run this command to create a DynamoDB table:
aws dynamodb create-table --table-name Orders --attribute-definitions AttributeName=Id,AttributeType=N --key-schema AttributeName=OrderId,KeyType=HASH --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5

But you get an error. What is the most likely cause?
medium
A. The attribute definition and key schema attribute names do not match
B. Provisioned throughput values are missing
C. The key schema is missing a RANGE key
D. AttributeType should be 'S' for string, not 'N' for number

Solution

  1. Step 1: Check attribute definitions and key schema names

    The attribute definitions specify AttributeName=Id, but the key schema specifies AttributeName=OrderId. The names do not match, causing the error.

  2. Step 2: Verify other potential issues

    Provisioned throughput values are present (not B), a simple primary key with only HASH is allowed (not C), AttributeType=N is valid for numeric IDs (not D).

  3. Final Answer:

    The attribute definition and key schema attribute names do not match -> Option A

  4. Quick Check:

    Attribute names must match exactly [OK]
Hint: Match attribute names exactly in definitions and key schema [OK]
Common Mistakes:
  • Assuming 'N' type is invalid
  • Expecting RANGE key for all tables
  • Missing provisioned throughput
5. You want to create a DynamoDB table named Sessions with a composite primary key: UserId (string) as HASH and SessionId (string) as RANGE. You also want to set autoscaling for read and write capacity. Which of the following is the best approach?
hard
A. Create the table without specifying key schema and add keys later
B. Use aws dynamodb create-table with attribute definitions and key schema, then configure autoscaling via Application Auto Scaling service
C. Use aws dynamodb create-table with only HASH key and enable autoscaling in the same command
D. Create the table with fixed provisioned throughput and manually update capacity when needed

Solution

  1. Step 1: Define table with composite primary key

    Use create-table with attribute definitions for UserId and SessionId, and key schema with HASH and RANGE keys.

  2. Step 2: Configure autoscaling separately

    DynamoDB autoscaling is set up via Application Auto Scaling service after table creation; it cannot be enabled directly in create-table command.

  3. Final Answer:

    Use aws dynamodb create-table with attribute definitions and key schema, then configure autoscaling via Application Auto Scaling service -> Option B

  4. Quick Check:

    Composite key + separate autoscaling setup = Use aws dynamodb create-table with attribute definitions and key schema, then configure autoscaling via Application Auto Scaling service [OK]
Hint: Create table first, then set autoscaling separately [OK]
Common Mistakes:
  • Trying to enable autoscaling in create-table command
  • Skipping RANGE key for composite key
  • Creating table without key schema
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard