amazon-dynamodb

Designs, costs, and live-validates DynamoDB data layers from access patterns and design axioms.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill amazon-dynamodb-richardnroman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amazon-dynamodb
Source: https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform/tree/main/.agents/skills/amazon-dynamodb
Command: npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill amazon-dynamodb-richardnroman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, and includes scripts (resource) and references (resource) components.

What problem does it solve? DynamoDB designs fail in predictable ways — hot partitions, wrong GSI projections, unbounded Scans, surprise bills — and most mistakes are only discovered after deployment. This Skill produces a defensible DynamoDB data-layer design grounded in explicit access patterns and design axioms, with a monthly cost estimate and optional live benchmarking against real AWS resources before you commit. ## Core Features & Use Cases - Axiom-driven schema design: Enumerates access patterns, then chooses partition/sort keys, GSIs, single-table vs. multi-table layout, Streams, TTL, Global Tables, and capacity mode using a documented conflict-resolution ordering. - Cost estimation: Generates a monthly cost report from a JSON data model via scripts/calculate_costs.py, with per-attribute item-size walkthroughs to keep estimates accurate. - Live validation pipeline: Optionally deploys the schema to AWS, benchmarks it with an in-region Lambda (quick, standard, or representative load modes), generates a performance report, and tears everything down — with consent gates and spend guardrails at every billable step. - Use Case: You are designing a multi-tenant SaaS backend on DynamoDB. The Skill interviews you on per-entity operational requirements, produces the access-pattern list, schema, and per-pattern query plan, estimates the monthly bill, then deploys and load-tests the design in a sandbox account to surface hot-partition and GSI-amplification risks. ## Quick Start Ask the agent to design a DynamoDB data layer for your application by listing your entities and query requirements, and let it produce the access-pattern list, schema, and cost estimate.

Frequently Asked Questions about amazon-dynamodb

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

FAQPage Schema
How do I design a DynamoDB schema from access patterns?▼

Start by enumerating every access pattern with its RPS, items returned, item size, consistency, and authorization scope. The Skill then applies design axioms to choose partition and sort keys, GSIs, and table boundaries, producing a schema and per-pattern query plan.

How do I estimate monthly DynamoDB costs before deploying?▼

Describe your tables and access patterns in a dynamodb_data_model.json file and run scripts/calculate_costs.py against it. The calculator uses per-operation capacity formulas and your declared RPS and item sizes to produce a monthly cost report without touching AWS.

Should I use single-table or multi-table design in DynamoDB?▼

The Skill decides via axioms: co-locate entities sharing access patterns by default, but split tables when operational configs diverge — different PITR retention, Streams consumers, capacity modes, or independent restore requirements. Authorization boundaries also force partition-key separation.

Does the live validation stage require AWS access?▼

Yes, stages 3-6 create real tables, a Lambda, and an IAM role using boto3 with standard AWS credentials, and they incur real charges. The design and cost stages need no AWS access, and every billable step requires explicit user consent and passes a spend guardrail.

Why is my DynamoDB table throttling or running hot partitions?▼

Hot partitions come from skewed key distribution exceeding per-partition throughput ceilings. The Skill's representative benchmark mode uses zipf key sampling to reproduce hot-partition behavior on your deployed schema and reports hot versus cold partition latency so you can re-key before production.

Can I change a GSI projection or key schema after creation?▼

No, GSI projection type and key schema are immutable after creation. The only path is an additive migration: create a new GSI with the desired shape, let it populate, cut reads over, then drop the old index.