Bird
Raised Fist0
AWScloud~5 mins

Partition key and sort key in AWS - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Introduction
When you store data in a database, you need a way to organize it so you can find it quickly. Partition key and sort key help split and order your data in AWS DynamoDB tables, making data retrieval fast and efficient.
When you want to store user profiles and quickly find a user by their unique ID.
When you have orders data and want to find all orders for a customer sorted by date.
When you need to organize sensor data by device and timestamp for fast queries.
When you want to avoid slow searches by using keys that directly point to data.
When you want to group related items together and sort them within that group.
Config File - dynamodb-table.json
dynamodb-table.json
{
  "TableName": "Orders",
  "AttributeDefinitions": [
    {"AttributeName": "CustomerId", "AttributeType": "S"},
    {"AttributeName": "OrderDate", "AttributeType": "S"}
  ],
  "KeySchema": [
    {"AttributeName": "CustomerId", "KeyType": "HASH"},
    {"AttributeName": "OrderDate", "KeyType": "RANGE"}
  ],
  "ProvisionedThroughput": {
    "ReadCapacityUnits": 5,
    "WriteCapacityUnits": 5
  }
}

TableName: The name of the DynamoDB table.

AttributeDefinitions: Defines the data types of the keys; 'S' means string.

KeySchema: Defines the partition key (HASH) and sort key (RANGE).

ProvisionedThroughput: Sets how much read and write capacity the table has.

Commands
This command creates a DynamoDB table named 'Orders' with CustomerId as the partition key and OrderDate as the sort key. It sets the read and write capacity to 5 units each.
Terminal
aws dynamodb create-table --cli-input-json file://dynamodb-table.json
Expected OutputExpected
{ "TableDescription": { "TableName": "Orders", "TableStatus": "CREATING", "ProvisionedThroughput": { "NumberOfDecreasesToday": 0, "ReadCapacityUnits": 5, "WriteCapacityUnits": 5 }, "TableSizeBytes": 0, "ItemCount": 0, "KeySchema": [ { "AttributeName": "CustomerId", "KeyType": "HASH" }, { "AttributeName": "OrderDate", "KeyType": "RANGE" } ], "TableArn": "arn:aws:dynamodb:us-east-1:123456789012:table/Orders" } }
→
--cli-input-json - Specifies the JSON file with table configuration
This command checks the status and details of the 'Orders' table to confirm it was created successfully.
Terminal
aws dynamodb describe-table --table-name Orders
Expected OutputExpected
{ "Table": { "TableName": "Orders", "TableStatus": "ACTIVE", "KeySchema": [ { "AttributeName": "CustomerId", "KeyType": "HASH" }, { "AttributeName": "OrderDate", "KeyType": "RANGE" } ], "ProvisionedThroughput": { "ReadCapacityUnits": 5, "WriteCapacityUnits": 5 }, "TableSizeBytes": 0, "ItemCount": 0 } }
This command adds an order item to the 'Orders' table with CustomerId as the partition key and OrderDate as the sort key.
Terminal
aws dynamodb put-item --table-name Orders --item '{"CustomerId": {"S": "cust123"}, "OrderDate": {"S": "2024-06-01"}, "OrderAmount": {"N": "250"}}'
Expected OutputExpected
{}
This command retrieves all orders for the customer with ID 'cust123', using the partition key to find the group of items.
Terminal
aws dynamodb query --table-name Orders --key-condition-expression "CustomerId = :cid" --expression-attribute-values '{":cid": {"S": "cust123"}}'
Expected OutputExpected
{ "Items": [ { "CustomerId": {"S": "cust123"}, "OrderDate": {"S": "2024-06-01"}, "OrderAmount": {"N": "250"} } ], "Count": 1, "ScannedCount": 1 }
→
--key-condition-expression - Specifies the condition to find items by partition key
→
--expression-attribute-values - Defines the value for the key condition
Key Concept

If you remember nothing else from this pattern, remember: the partition key groups your data, and the sort key orders it within that group for fast and organized access.

Common Mistakes
Using only a partition key when you need to sort or filter items within a group.
Without a sort key, you cannot order or efficiently query items that share the same partition key.
Add a sort key to your table schema when you want to organize items within each partition.
Using a sort key as the partition key or mixing their roles.
The partition key determines data distribution and must be unique per group; the sort key orders items within that group.
Define the partition key as the main grouping attribute and the sort key as the secondary ordering attribute.
Querying without specifying the partition key in the key condition expression.
DynamoDB requires the partition key to be specified to efficiently find items; omitting it causes errors or full scans.
Always include the partition key in your query's key condition expression.
Summary
Create a DynamoDB table with a partition key and sort key to organize and order data.
Use the partition key to group related items and the sort key to sort them within the group.
Query the table by specifying the partition key to quickly find all related items.

Practice

(1/5)
1.

What is the main role of a partition key in AWS DynamoDB?

easy
A. It groups data into partitions for efficient storage and retrieval.
B. It sorts data within a partition in ascending order.
C. It encrypts the data before storing it.
D. It defines the backup schedule for the table.

Solution

  1. Step 1: Understand partition key purpose

    The partition key is used to group data into partitions, which helps DynamoDB distribute and store data efficiently.

  2. Step 2: Differentiate from sort key

    The sort key orders data inside each partition but does not group data across partitions.

  3. Final Answer:

    It groups data into partitions for efficient storage and retrieval. -> Option A

  4. Quick Check:

    Partition key = groups data [OK]
Hint: Partition key groups data, sort key orders it inside partitions [OK]
Common Mistakes:
  • Confusing partition key with sort key
  • Thinking partition key sorts data
  • Assuming partition key controls backups
2.

Which of the following is the correct way to define a DynamoDB table with a partition key named UserId and a sort key named OrderDate in AWS CLI?

aws dynamodb create-table --table-name Orders --attribute-definitions AttributeName=UserId,AttributeType=S AttributeName=OrderDate,AttributeType=S --key-schema ...
easy
A. --key-schema AttributeName=UserId,KeyType=HASH AttributeName=OrderDate,KeyType=RANGE
B. --key-schema AttributeName=OrderDate,KeyType=HASH AttributeName=UserId,KeyType=RANGE
C. --key-schema AttributeName=UserId,KeyType=RANGE AttributeName=OrderDate,KeyType=HASH
D. --key-schema AttributeName=OrderDate,KeyType=RANGE AttributeName=UserId,KeyType=HASH

Solution

  1. Step 1: Identify partition and sort key roles

    The partition key uses KeyType=HASH and the sort key uses KeyType=RANGE in DynamoDB key schema.

  2. Step 2: Match keys to names

    UserId is the partition key (HASH), OrderDate is the sort key (RANGE).

  3. Final Answer:

    --key-schema AttributeName=UserId,KeyType=HASH AttributeName=OrderDate,KeyType=RANGE -> Option A

  4. Quick Check:

    Partition=HASH, Sort=RANGE [OK]
Hint: Partition key = HASH, sort key = RANGE in key schema [OK]
Common Mistakes:
  • Swapping HASH and RANGE key types
  • Mixing up partition and sort key names
  • Using wrong attribute types
3.

Given a DynamoDB table with CustomerId as partition key and InvoiceDate as sort key, what will the following query return?

Query: KeyConditionExpression = "CustomerId = :cid AND InvoiceDate > :date"

Assuming :cid is '123' and :date is '2023-01-01'.

medium
A. All invoices for customer '123' regardless of date.
B. All invoices for customer '123' with dates after January 1, 2023.
C. All invoices for all customers with dates after January 1, 2023.
D. All invoices with dates before January 1, 2023.

Solution

  1. Step 1: Understand KeyConditionExpression

    The query filters items where partition key CustomerId equals '123' and sort key InvoiceDate is greater than '2023-01-01'.

  2. Step 2: Interpret the filter effect

    This returns all invoices for customer '123' with InvoiceDate after January 1, 2023.

  3. Final Answer:

    All invoices for customer '123' with dates after January 1, 2023. -> Option B

  4. Quick Check:

    Partition key = '123' AND sort key > '2023-01-01' [OK]
Hint: Partition key filters customer, sort key filters date range [OK]
Common Mistakes:
  • Ignoring partition key filter
  • Assuming query returns all customers
  • Confusing greater than with less than
4.

What is wrong with this DynamoDB key schema definition?

--attribute-definitions AttributeName=OrderId,AttributeType=S AttributeName=OrderDate,AttributeType=S --key-schema AttributeName=OrderDate,KeyType=HASH AttributeName=OrderId,KeyType=RANGE
medium
A. Attribute names cannot contain uppercase letters.
B. Attribute types must be different for partition and sort keys.
C. KeyType values must both be HASH for composite keys.
D. Partition key and sort key are swapped; OrderId should be HASH, OrderDate RANGE.

Solution

  1. Step 1: Check key roles

    Partition key must be HASH and sort key must be RANGE in key schema.

  2. Step 2: Identify swapped keys

    OrderId should be the partition key (HASH), but here OrderDate is set as HASH and OrderId as RANGE, which is incorrect.

  3. Final Answer:

    Partition key and sort key are swapped; OrderId should be HASH, OrderDate RANGE. -> Option D

  4. Quick Check:

    Partition = HASH, Sort = RANGE order matters [OK]
Hint: Partition key always HASH, sort key always RANGE [OK]
Common Mistakes:
  • Swapping HASH and RANGE key types
  • Assuming attribute types must differ
  • Thinking uppercase letters are invalid
5.

You want to design a DynamoDB table to store user activity logs. Each user can have multiple logs per day. Which key design is best to efficiently query all logs for a user on a specific day?

hard
A. Partition key: UserId, Sort key: ActivityDateTime
B. Partition key: ActivityDateTime, Sort key: UserId
C. Partition key: UserId_ActivityDate, Sort key: ActivityTime
D. Partition key: ActivityType, Sort key: UserId

Solution

  1. Step 1: Understand query needs

    You want to query logs by user and by specific day efficiently.

  2. Step 2: Design keys for efficient queries

    Combining UserId and ActivityDate as partition key groups logs per user per day. Using ActivityTime as sort key orders logs within that day.

  3. Final Answer:

    Partition key: UserId_ActivityDate, Sort key: ActivityTime -> Option C

  4. Quick Check:

    Composite partition key groups user-day logs [OK]
Hint: Combine user and date in partition key for day queries [OK]
Common Mistakes:
  • Using ActivityDateTime as partition key alone
  • Swapping partition and sort keys
  • Not combining keys to match query pattern
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