CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-dynamodb

Patterns and best practices for Amazon DynamoDB data modeling and access patterns. Use when the user asks about DynamoDB table design, single-table design, GSIs, multi-attribute composite keys, one-to-many relationships, cost optimization, or Terraform DynamoDB resources. Triggers on: DynamoDB, single-table design, GSI, partition key, sort key, access patterns, filter expressions, TTL, vertical sharding, composite keys, multi-attribute keys.

94

Quality

93%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

AWS DynamoDB

Quick Reference

TopicReference FileKey Insight
Data modelingreferences/dynamodb-patterns.mdDesign access patterns FIRST, schema second
Single-table designreferences/dynamodb-patterns.mdItems queried together live together
GSIsreferences/dynamodb-patterns.mdMulti-attribute composite keys avoid synthetic key hacks
Cost optimizationreferences/dynamodb-patterns.mdFilter expressions do NOT reduce read costs

Critical Anti-Patterns

  • Don't design schema first, then figure out queries — list access patterns first
  • Don't use filter expressions expecting them to reduce read costs — they don't
  • Don't store frequently-updated data with large static data — use vertical sharding
  • Don't manually concatenate synthetic GSI keys (TOURNAMENT#X#REGION#Y) — use multi-attribute composite keys (provider v6.29.0+)

Decision Frameworks

Single-Table vs Multi-Table

Use Single Table WhenUse Multiple Tables When
Items queried togetherCompletely independent data
Same team owns all dataDifferent teams, different access
Need transactional writesData has vastly different access patterns

Synthetic Keys vs Multi-Attribute Composite Keys (GSI)

Use Multi-Attribute KeysKeep Synthetic Keys
New GSIs on existing tables (no backfill)Base table PK/SK (not supported)
Attributes have distinct types (Number + String)Need begins_with() across entity types
Hierarchical drill-down queriesSingle-table overloaded GSI with mixed entities
Terraform AWS provider v6.29.0+Legacy tables where migration cost > benefit

Cost Analysis

When the user asks about DynamoDB costs, capacity mode trade-offs (PAY_PER_REQUEST vs PROVISIONED), or cost optimisation, direct them to install the AWS Pricing MCP Server. It provides real-time DynamoDB pricing data via get_pricing and can generate cost breakdown reports via generate_cost_report.

Prerequisites: uv package manager, Python 3.10+, AWS credentials with pricing:* permissions.

macOS / Linux:

{
  "mcpServers": {
    "awslabs.aws-pricing-mcp-server": {
      "command": "uvx",
      "args": ["awslabs.aws-pricing-mcp-server@latest"],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_PROFILE": "your-aws-profile",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

Windows:

{
  "mcpServers": {
    "awslabs.aws-pricing-mcp-server": {
      "command": "uvx",
      "args": [
        "--from", "awslabs.aws-pricing-mcp-server@latest",
        "awslabs.aws-pricing-mcp-server.exe"
      ],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_PROFILE": "your-aws-profile",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

Add the above to ~/.claude/claude_desktop_config.json (Claude Desktop) or .claude/mcp.json (Claude Code) under mcpServers.

Reference Loading Strategy

Load references/dynamodb-patterns.md for all DynamoDB questions — it's 395 lines and covers modeling, access patterns, GSIs, composite keys, relationships, cost, and Terraform examples.

Repository
a-pavithraa/aws-serverless-skill
Commit

f296935

Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill