dynamodb

Design DynamoDB schemas, indexes, and query patterns with troubleshooting guidance.

Updated Feb 16, 2026

Search Tags:#query optimization #schema design #dynamodb #ttl #single-table design #gsi lsi #throughput throttling

Ready to run

npx skills add https://github.com/aurainfosec/cloud-review-automation-poc --skill dynamodb-aurainfosec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dynamodb
Source: https://github.com/aurainfosec/cloud-review-automation-poc/tree/main/skills/dynamodb
Command: npx skills add https://github.com/aurainfosec/cloud-review-automation-poc --skill dynamodb-aurainfosec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you model DynamoDB tables and indices and then troubleshoot performance or correctness issues so your access patterns work reliably at scale.

Core Features & Use Cases

Schema and access-pattern guidance: Use partition/sort keys, GSIs/LSIs, and common patterns like single-table design to match how your application reads data.
Practical operational workflows: Cover table/index operations, CRUD/query patterns, batch/transaction patterns, and TTL usage to support real application lifecycles.
Debugging and performance mitigation: Diagnose issues such as throttling and hot partitions and apply mitigation tactics like better key distribution and retry strategies.

Quick Start

Use the dynamodb skill to design a single-table schema for users and orders, then generate example query patterns to fetch a user profile and recent orders.

Frequently Asked Questions about dynamodb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a single-table schema in DynamoDB for multiple access patterns?▼

DynamoDB single-table design models multiple entities in one table by carefully defining partition and sort keys to ensure all application read patterns are supported by efficient key-based queries. This approach prevents the need for multiple tables and complex joins.

Why is my DynamoDB query returning empty results or facing throttling issues?▼

DynamoDB throttling and empty query results often stem from hot partitions caused by uneven key distribution or incorrect index selection. Diagnose access patterns and apply mitigation tactics like better key distribution and retry strategies to resolve these operational failures.

When should I use a GSI versus an LSI in DynamoDB index design?▼

DynamoDB GSIs support querying across alternative partition keys and are updated asynchronously, while LSIs are limited to querying the same partition key with different sort keys. Choose GSIs for flexible access patterns and LSIs for strongly consistent reads within a single partition.

What is the best way to handle time-to-live (TTL) and data expiration in DynamoDB?▼

DynamoDB TTL automatically deletes expired items from your table without consuming write capacity. Define a specific attribute as the TTL timestamp to let the background process remove expired records, efficiently supporting application lifecycles and reducing storage costs.

How do I troubleshoot hot partitions and manage throughput capacity in DynamoDB?▼

DynamoDB hot partitions occur when access is concentrated on a single partition key. Mitigate this by improving key distribution across partitions and adjusting capacity modes to handle throughput throttling, ensuring reliable performance at scale.