[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A72VDXAJ7PA4N1DP67BAJR":3,"skill-same:01M7A72VDXAJ7PA4N1DP67BAJR":146},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7A72VDXAJ7PA4N1DP67BAJR","dynamodb-table-deployer",null,"Provisions DynamoDB tables with production-grade defaults: partition key design (random suffix, composite keys), sort key design (range queries, hierarchical data), GSI design (sparse indexes, ALL\u002FKEYS_ONLY\u002FINCLUDE projection), on-demand vs provisioned capacity choice, PITR enabled by default, SSE-KMS with customer-managed CMK for compliance, TTL configuration, DynamoDB Streams (NEW_AND_OLD_IMAGES for CDC), table class (Standard vs Standard-IA), deletion protection, and resource-based policies. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a new DynamoDB table, hardening an existing table for production, validating schema\u002Fkey design before go-live, designing GSIs for alternate access patterns, or generating a Terraform \u002F CloudFormation skeleton. Triggers: create DynamoDB table, provision DynamoDB, partition key design, GSI design, DynamoDB Streams, TTL configuration, global tables, Aurora zero-ETL, OpenSearch zero-ETL.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dynamodb-table-deployer\ndescription: 'Provisions DynamoDB tables with production-grade defaults: partition key design (random suffix, composite keys), sort key design (range queries, hierarchical data), GSI design (sparse indexes, ALL\u002FKEYS_ONLY\u002FINCLUDE projection), on-demand vs provisioned capacity choice, PITR enabled by default, SSE-KMS with customer-managed CMK for compliance, TTL configuration, DynamoDB Streams (NEW_AND_OLD_IMAGES for CDC), table class (Standard vs Standard-IA), deletion protection, and resource-based policies. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a new DynamoDB table, hardening an existing table for production, validating schema\u002Fkey design before go-live, designing GSIs for alternate access patterns, or generating a Terraform \u002F CloudFormation skeleton. Triggers: create DynamoDB table, provision DynamoDB, partition key design, GSI design, DynamoDB Streams, TTL configuration, global tables, Aurora zero-ETL, OpenSearch zero-ETL.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with dynamodb, application- autoscaling, kms, and iam access. Works with Terraform aws_dynamodb_table resources and CloudFormation AWS::DynamoDB::Table templates.'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Databases\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: experimental\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, dynamodb, cloudops, deploy, databases, provisioning, partition-key, gsi, pitr, sse-kms, ttl, streams, deletion-protection\n  dependencies: aws-orchestrator\n  keywords: aws, dynamodb, cloudops, deploy, provisioning, partition key, sort key, gsi, global secondary index, lsi, on-demand, provisioned, pay per request, autoscaling, pitr, point-in-time recovery, sse-kms, ttl, time to live, dynamodb streams, cdc, table class, standard-ia, deletion protection, global tables, zero-etl, aurora zero-etl, opensearch zero-etl\n  when_to_use: Invoke when the user wants to create a new DynamoDB table with production defaults, design a partition\u002Fsort key scheme, plan GSI access patterns, harden an existing table before production, validate key\u002Fschema design before go-live, plan CDC pipelines via DynamoDB Streams, set up global tables, or generate provisioning CLI commands \u002F IaC templates. Do NOT invoke for auditing existing table posture (use dynamodb-table-auditor), or for non-DynamoDB NoSQL (DocumentDB, ElastiCache, Neptune, Timestream).\n---\n\n# DynamoDB Table Deployer\n\nAn AWS CloudOps agent skill that provisions DynamoDB tables with correct\ndefaults. The skill walks the operator through a 10-step provisioning\nprocedure, captures the operator's access-pattern decisions (partition key,\nsort key, GSI projections, capacity mode), explains why each default matters,\nand emits a READY_TO_DEPLOY checklist with copy-pasteable verification\ncommands.\n\n## Activation keywords\n\ncreate DynamoDB table, provision DynamoDB, DynamoDB deployment, partition key\ndesign, sort key design, hot partition, random suffix, composite key, GSI\ndesign, sparse index, ALL projection, KEYS_ONLY projection, INCLUDE\nprojection, on-demand capacity, provisioned capacity, PAY_PER_REQUEST,\nautoscaling, PITR, point-in-time recovery, SSE-KMS, customer-managed CMK,\nDynamoDB TTL, item expiration, DynamoDB Streams, NEW_AND_OLD_IMAGES,\nCDC pipeline, table class, Standard-IA, deletion protection, global tables,\nAurora zero-ETL, OpenSearch zero-ETL, resource-based policy.\n\n## Invocation contract (hard requirement)\n\nWhen this skill is invoked with a table-provisioning request (table name,\naccess pattern, workload shape, region, or a partial configuration), the\nagent MUST respond with the READY_TO_DEPLOY checklist defined in\n§\"Output format\" using the literal all-caps labels `TABLE:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines\nof the response. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels breaks\nautomation silently.\n\n## Mindset\n\nThree provisioning misconceptions (natural-key hot partitions, on-demand burst bucket, GSI cost cascade) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when explaining why creation-time decisions matter.\n\n## Reasoning framework (why provisioning order matters)\n\nSix ordering rules (key schema before first write, LSI creation-only, capacity mode before traffic, GSI autoscaling at creation, SSE-KMS before first write, additive settings early) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when sequencing the provisioning run.\n\n## DynamoDB configuration dependency graph (novel heuristic)\n\nConfiguration dependency graph (13-row immutability\u002Fsilent-failure matrix plus cross-dependency gotchas) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when a configuration interaction is unclear.\n\n## Expert heuristic: partition key cardinality calculator\n\nPartition key cardinality calculator (10,000-distinct-values rule, quick-check formula, common scenarios) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when sizing a write-heavy partition key.\n\n## Expert heuristic: GSI cost multiplier\n\nGSI cost multiplier (ceil(item_size_kb) x gsi_count, 12-WCU worked example, 30%-of-bill budget heuristic) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand before adding the 3rd GSI.\n\n## Expert heuristic: adaptive capacity false sense of security\n\nAdaptive capacity deep dive (~30-second borrow window, what it does NOT do, throttling signature, on-demand burst bucket) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when throttling appears despite adequate capacity.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If any\nare missing, the verdict is **PREREQUISITES_MISSING** with a specific gap\ncitation.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| AWS account with DynamoDB access | Can't provision without it | `aws sts get-caller-identity` |\n| Region selected | Capacity, KMS, and Streams are region-scoped | `aws configure get region` |\n| Table name available and unique in this region (and globally if Global Tables planned) | Names are region-unique; Global Tables require unique name across all replica regions | `aws dynamodb describe-table --table-name \u003Cname>` returns `ResourceNotFoundException` |\n| KMS key ARN (if SSE-KMS with customer CMK) | Custom encryption requires a CMK in the same region with a key policy granting DynamoDB | `aws kms describe-key --key-id \u003Ccmk-id>` |\n| Access-pattern description | Key schema, sort key, and GSI design are access-pattern-driven and immutable | Captured in the prompt or follow-up question |\n| CMK key policy grants DynamoDB service + calling principal | SSE-KMS requires `kms:GenerateDataKey` + `kms:Decrypt` grants | `aws kms get-key-policy --key-id \u003Ccmk-id> --policy-name default` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING` and\ncite the specific gap.\n\n## 10-step provisioning procedure\n\n### Step 1 — Partition key design (immutable — decide BEFORE create-table)\n\nThe partition key determines how writes distribute across physical\npartitions. A bad partition key is the single highest-impact DynamoDB\ndesign mistake and is **immutable** after creation.\n\n**Decision tree:**\n\n- **High-cardinality, even-distribution workload** (session store, ad-tech\n  events, IoT telemetry, user-profile keying by `userId`): use the natural\n  high-cardinality attribute directly. Verify with a histogram of the\n  attribute if possible.\n\n- **Monotonically increasing attribute as the natural key** (timestamp,\n  auto-increment id, sequential orderId): append a **random suffix** (e.g.,\n  0-99 or a hash bucket) and use `\u003CnaturalKey>#\u003Csuffix>` as the partition\n  key. Distributes writes across N buckets → N physical partitions.\n\n  ```text\n  orderId: 100001  →  partition key: \"100001#37\"\n  orderId: 100002  →  partition key: \"100002#04\"\n  orderId: 100003  →  partition key: \"100003#71\"\n  ```\n\n  The application generates the suffix (random or hash of an unrelated\n  attribute); reads must fan out across all suffixes if the natural key\n  must be reconstructed. This is the canonical fix for hot-partition\n  write throttling.\n\n- **Composite key for hierarchical data** (multi-tenant, time-bucketed):\n  combine tenantId + bucketId into the partition key (e.g.,\n  `\u003CtenantId>#\u003Cyyyy-mm>`), use a sort key for the intra-bucket ordering.\n  Distributes tenants across partitions while keeping tenant data\n  co-located for efficient queries.\n\n- **Low-cardinality attribute (status, category, boolean)**: NEVER use as\n  the partition key alone — writes will concentrate on 1-few partitions.\n  Combine with a high-cardinality attribute to form a composite key.\n\n**Why decided at creation**: the partition key is part of `KeySchema` in\n`create-table` and is immutable. Re-keying an existing table means\ncreate-new → backfill (with re-partitioning) → cutover. Decide before the\nfirst write.\n\n**Common mistake**: using a timestamp-prefix partition key for time-series\ndata. All writes in the current second\u002Fminute\u002Fhour hit one partition\n(DynamoDB hashes the partition key, but a low-cardinality timestamp prefix\nstill concentrates writes within a time bucket). Use the random-suffix\npattern OR use the sort key for time within a high-cardinality partition.\n\n### Step 2 — Sort key design (immutable — decide BEFORE create-table)\n\nThe sort key enables range queries (`between`, `begins_with`) within a\npartition. Decide at creation; sort key is immutable.\n\n**Decision tree:**\n\n- **Time-range queries within an entity** (orders for a user, events for\n  a session, messages in a thread): partition key = entity id, sort key =\n  timestamp (ISO 8601 or epoch). Enables `Query` with\n  `KeyConditionExpression: pk = :entity AND sk BETWEEN :start AND :end`.\n\n- **Hierarchical data** (category\u002Fsubcategory paths, file paths): sort key\n  = path (e.g., `category\u002Fsubcategory\u002Fitem`). Enables `begins_with`\n  queries for subtree retrieval.\n\n- **Latest-item lookup** (leaderboards, current state): use a sort key that\n  sorts newest-first. For numeric\u002Fepoch sort keys, store the negation or\n  `MAX_VALUE - timestamp` so the latest sorts first.\n\n- **No range-query need**: omit the sort key (table can have partition key\n  only). Adding a sort key later requires re-creating the table.\n\n**Common mistake**: planning to use a non-key attribute for range queries\npost-creation. Either (a) add it as the sort key now (immutable), (b) add\nan LSI now (immutable, only-at-creation, 5-per-table limit), or (c) add a\nGSI later (mutable but with capacity\u002Fcascade implications).\n\n### Step 3 — Local Secondary Indexes (LSI) — decide NOW or forever hold peace\n\nLSIs enable range queries on a non-key sort attribute within the SAME\npartition key as the base table. They can ONLY be created at `create-table`\ntime — there is NO API to add an LSI later.\n\n**Hard limits** (do not exceed):\n- 5 LSIs per table (HARD API-enforced limit — cannot be raised via support ticket).\n- 10 GB per-partition size limit on indexed data (silently rejects writes past this point — must monitor per-partition index size).\n\n**When to provision an LSI at creation:**\n- Workload needs strong consistency on the alternate sort attribute (LSI\n  supports eventually-consistent AND strongly-consistent reads; GSI only\n  eventually-consistent).\n- Workload needs range queries within the base table's partition key on a\n  different sort attribute.\n\n**When to defer to a GSI (added later):**\n- The alternate access pattern uses a DIFFERENT partition key (LSI shares\n  the base partition key).\n- Eventual consistency is acceptable.\n- You are unsure — GSIs are reversible; LSIs are not.\n\n**Common mistake**: deciding to \"add the LSI later.\" There is no later.\nIf the workload MIGHT need range queries on a non-key attribute, decide\nat creation. Document the decision in the checklist.\n\n### Step 4 — Global Secondary Indexes (GSI) — design at provisioning\n\nGSIs enable alternate access patterns with a different partition key. They\nCAN be added post-creation, but each GSI has its own capacity, its own\nthrottle cascade back to the base table, and counts toward the 20-per-table\nsoft quota.\n\n**Projection type decision (drives storage cost + write amplification):**\n\n| Projection | What it stores | Write cost | Storage cost | Use when |\n|---|---|---|---|---|\n| `ALL` | Entire base-table item | highest (every base write replicates fully) | highest | GSI is read-heavy and you want to avoid a follow-up GetItem |\n| `INCLUDE` | Keys + specified non-key attributes | medium (only listed attributes projected) | medium | GSI needs a few specific attributes (e.g., status, name) |\n| `KEYS_ONLY` | Only the GSI's key attributes | lowest (minimum replication) | lowest | GSI is a lookup index; follow up with GetItem from the base table for full data |\n\n**Sparse index pattern**: a GSI where the sort key attribute only exists\non SOME items becomes a sparse index — only items with that attribute\nappear in the GSI. Powerful for \"find all items in state X\" queries\nwithout scanning the whole table.\n\n**Capacity per GSI (PROVISIONED mode)**: each GSI has its OWN RCU\u002FWCU\nallocation. A GSI with insufficient WCU throttles BASE TABLE writes —\nthe cascade rule. Always register autoscaling on every GSI in PROVISIONED\nmode (Step 5).\n\n**Quota check**: the 20-GSI-per-table soft limit can be raised via support\nticket. The 5-LSI limit cannot. Plan GSI count at provisioning.\n\n**Common mistake**: provisioning a GSI with `ALL` projection \"for\nconvenience.\" Every base-table write now fully replicates to the GSI,\ndoubling write cost. Default to `KEYS_ONLY` and follow up with a `GetItem`;\nupgrade to `INCLUDE` only for known hot attributes.\n\n### Step 5 — Capacity mode + autoscaling\n\nChoose between `PAY_PER_REQUEST` (on-demand) and `PROVISIONED` with\nautoscaling based on the **traffic profile**, not on a desire to avoid\ncapacity planning.\n\n**Decision matrix:**\n\n| Traffic profile | Recommended mode | Why |\n|---|---|---|\n| Unknown \u002F new workload | `PAY_PER_REQUEST` (on-demand) | No capacity planning needed; pay per request |\n| Bursty \u002F unpredictable | `PAY_PER_REQUEST` (on-demand) | Autoscaling has 3-5 min lag; on-demand handles spikes (within burst bucket) |\n| Steady high-throughput | `PROVISIONED` + autoscaling | 3-5x cheaper than on-demand at sustained load |\n| Idle \u002F dev \u002F test | `PAY_PER_REQUEST` (on-demand) | Pay zero when table is idle; provisioned has minimum capacity charges |\n| Once-per-hour batch | `PAY_PER_REQUEST` (on-demand) | Cold-start burst bucket handles the spike better than provisioned scale-out lag |\n\nOn-demand burst bucket caveat (trailing 30-minute average, empty on cold start) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when on-demand is chosen for bursty traffic.\n\nPROVISIONED autoscaling registration CLI (register-scalable-target + TargetTrackingScaling policies, per-GSI repeat) moved verbatim to [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md).\nLoad on demand when provisioning a PROVISIONED table.\n\n**Common mistake**: registering autoscaling on the base table but NOT on\na GSI. The GSI throttles and cascades back to the base table — the most\ncommonly missed capacity misconfiguration.\n\n**Switching modes**: DynamoDB enforces a cooldown between\nPAY_PER_REQUEST ↔ PROVISIONED switches. Don't switch per-request.\n\n### Step 6 — Encryption (SSE-KMS)\n\nDynamoDB ALWAYS encrypts at rest. The decision is whether to use\nAWS-managed or customer-controlled encryption:\n\n| Option | SSEType | Key policy control | CloudTrail visibility | Use when |\n|---|---|---|---|---|\n| Default (AWS-owned key) | `AES256` | none | none | dev \u002F test \u002F non-compliance workloads |\n| AWS-managed KMS key (`alias\u002Faws\u002Fdynamodb`) | `KMS` | limited (DynamoDB-managed) | partial | when KMS API visibility matters but key policy does not |\n| Customer-managed CMK | `KMS` with explicit `KMSMasterKeyArn` | full (you set the policy) | full (per-call Decrypt events) | compliance (PCI-DSS, HIPAA, SOC2), cross-account, regulated data |\n\n**For compliance workloads**, always use a customer-managed CMK and verify\nthe key policy grants `kms:GenerateDataKey` + `kms:Decrypt` to both\n`dynamodb.\u003Cregion>.amazonaws.com` and the calling principal.\n\n```bash\naws dynamodb create-table ... \\\n  --sse-specification Enabled=true,SSEType=KMS,KMSMasterKeyId=arn:aws:kms:\u003Cregion>:\u003Cacct>:key\u002F\u003Ccmk-id>\n```\n\nKMS cost warning (quota sharing vs the dedicated aws\u002Fdynamodb quota) and the Global Tables CMK-per-region requirement moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when provisioning SSE-KMS at high throughput or multi-region.\n\n### Step 7 — Point-in-time recovery (PITR) — enable by default\n\nPITR enablement CLI, new-table restore semantics, and cost note moved verbatim to [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md).\nLoad on demand when enabling PITR.\n\n### Step 8 — TTL configuration (optional — automatic item expiration)\n\nTTL automatically deletes items whose specified attribute (epoch seconds)\nis in the past. Use for: session expiry, log retention, cache eviction,\nGDPR data-retention enforcement (with caveats below).\n\n```bash\naws dynamodb update-time-to-live --table-name \u003Ctable> \\\n  --time-to-live-specification Enabled=true,AttributeName=ttl\n```\n\n**TTL semantics** (do not misrepresent):\n- Items WITHOUT the TTL attribute are NEVER expired.\n- Deletion is by background scanner within **48 hours** of the expiry\n  timestamp. Items remain readable until physically deleted.\n- TTL is a **cost-optimization feature**, NOT a compliance enforcement\n  mechanism. For immediate\u002Fverifiable deletion, the application must\n  explicitly `DeleteItem`.\n\n**Common mistake**: relying on TTL for GDPR immediate-deletion. The 48-hour\nlag and the \"items without attribute are never expired\" rule both break\nthe contract.\n\n### Step 9 — Streams + table class + deletion protection\n\nStreams StreamViewType selection, table class choice, and deletion protection CLI moved verbatim to [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md).\nLoad on demand when configuring Streams, class, or deletion protection.\n\n### Step 10 — Resource-based policy + Global Tables (newer features)\n\nResource-based policy JSON, Global Tables v2 creation CLI, and the 2024-2026 integration notes (OpenSearch zero-ETL, Aurora zero-ETL, replication metrics) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when provisioning cross-account or multi-region tables.\n\n## NEVER do these things\n\n1. **NEVER pick a partition key without considering cardinality and write\n   distribution.** A monotonically increasing key (timestamp, auto-increment\n   id) creates a hot partition and throttles the table far below its\n   provisioned capacity. Use a random suffix or composite key. Re-keying\n   requires create-new + backfill + cutover.\n\n2. **NEVER plan to \"add the LSI later.\"** Local Secondary Indexes can ONLY\n   be created at `create-table` time. There is NO API to add an LSI\n   post-creation. Decide LSI placement at provisioning or commit to a GSI.\n\n3. **NEVER register autoscaling on the base table but forget the GSIs.**\n   A GSI with insufficient WCU throttles writes to the BASE TABLE — the\n   cascade rule. Register autoscaling on every GSI in PROVISIONED mode.\n\n4. **NEVER use the AWS-managed `alias\u002Faws\u002Fdynamodb` key for compliance\n   workloads (PCI-DSS \u002F HIPAA \u002F SOC2 \u002F FedRAMP).** You cannot customize\n   the key policy. Use a customer-managed CMK with explicit\n   `kms:GenerateDataKey` + `kms:Decrypt` grants.\n\n5. **NEVER rely on TTL for immediate data deletion or GDPR compliance.**\n   TTL items persist for up to 48 hours after expiry. Items without the\n   TTL attribute are never expired. TTL is a cost-optimization feature,\n   not a compliance enforcement mechanism.\n\n6. **NEVER assume on-demand mode eliminates capacity risk.** On-demand\n   has a finite burst bucket derived from the trailing 30 minutes. A\n   cold-start spike from zero can still throttle. Flag this as\n   operational guidance.\n\n7. **NEVER enable Streams as a \"default hardening\" step on tables whose\n   workload does not consume CDC.** Streams incur write-amplification cost\n   and have a 24-hour retention window. Enable Streams only when there is\n   a downstream consumer (Lambda, OpenSearch sync, Kinesis, Aurora zero-ETL).\n\n8. **NEVER exceed the 5-LSI-per-table limit.** It is a HARD API-enforced\n   limit — cannot be raised via support ticket. The 20-GSI soft limit\n   CAN be raised. Plan accordingly at provisioning.\n\n9. **NEVER provision a Global Table replica in a region without the CMK\n   present.** A missing key causes `InaccessibleEncryptionDateTime` —\n   an active outage on that replica. Verify `aws kms describe-key` in\n   every replica region before adding the replica.\n\n10. **NEVER treat `DeletionProtectionEnabled` as a security control.**\n    Any principal with `dynamodb:UpdateTable` can disable it. It is an\n    accidental-deletion \u002F ransomware guardrail, not a defense against a\n    determined attacker with database-admin rights.\n\n11. **NEVER switch billing mode for per-request cost optimization.**\n    DynamoDB enforces a cooldown between `PAY_PER_REQUEST` and `PROVISIONED`\n    switches. Choose based on the sustained traffic profile.\n\n12. **NEVER use `ALL` projection on a GSI \"for convenience.\"** Every\n    base-table write fully replicates, doubling write cost. Default to\n    `KEYS_ONLY` and follow up with a `GetItem`; upgrade to `INCLUDE` for\n    known hot attributes.\n\n## Output format\n\n```text\nTABLE: \u003Ctable-name>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Partition key: \u003Cattribute> (\u003Ctype>) — \u003Cdesign rationale>\n  [✓|✗] Sort key: \u003Cattribute> (\u003Ctype>) | None\n  [✓|✗] LSIs: \u003Clist with sort attributes> | None (5-max HARD limit respected)\n  [✓|✗] GSIs: \u003Clist with projection types> | None\n  [✓|✗] Capacity mode: PAY_PER_REQUEST | PROVISIONED (autoscaling: table ✓ \u003Cgsi> ✓)\n  [✓|✗] Encryption: SSE-KMS customer CMK (\u003Ckey-arn>) | AWS-managed (alias\u002Faws\u002Fdynamodb) | AES256\n  [✓|✗] PITR: Enabled (35-day window)\n  [✓|✗] TTL: Enabled (attribute: \u003Cname>) | Disabled\n  [✓|✗] Streams: NEW_AND_OLD_IMAGES | KEYS_ONLY | NEW_IMAGE | OLD_IMAGE | Disabled\n  [✓|✗] Table class: STANDARD | STANDARD_INFREQUENT_ACCESS\n  [✓|✗] Deletion protection: Enabled | Disabled\n  [✓|✗] Resource-based policy: \u003Csummary> | None\n  [✓|✗] Global Tables: replicas in \u003Cregions> | Single-region\nVERIFICATION_COMMANDS:\n  aws dynamodb describe-table --table-name \u003Ctable>\n  aws dynamodb describe-continuous-backups --table-name \u003Ctable>\n  aws dynamodb describe-time-to-live --table-name \u003Ctable>\n  aws dynamodb describe-kinesis-destination --table-name \u003Ctable>   # if Kinesis fan-out\n  aws application-autoscaling describe-scaling-policies --service-namespace dynamodb\n  aws kms describe-key --key-id \u003Ccmk-id>\n```\n\n### Worked example — high-throughput session store\n\n```text\nTABLE: prod-sessions\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Partition key: sessionId (String) — UUID v4, high-cardinality for even write distribution\n  [✓] Sort key: None (single-item lookup pattern)\n  [✓] LSIs: None (no range-query requirement on alternate sort attribute)\n  [✓] GSIs: gsi_by_userId (userId→sessionId, KEYS_ONLY projection, sparse — only items with userId)\n  [✓] Capacity mode: PAY_PER_REQUEST (bursty session traffic, unpredictable peaks)\n  [✓] Encryption: SSE-KMS customer CMK (alias\u002Fprod-dynamodb-key)\n  [✓] PITR: Enabled (35-day window)\n  [✓] TTL: Enabled (attribute: expiresAt — session token expiry, ~48h lag acceptable)\n  [✓] Streams: NEW_AND_OLD_IMAGES (downstream Lambda publishes session-change events)\n  [✓] Table class: STANDARD (frequently accessed)\n  [✓] Deletion protection: Enabled\n  [✓] Resource-based policy: Allow read-only from analytics account 222222222222\n  [✓] Global Tables: Single-region (us-east-1)\nVERIFICATION_COMMANDS:\n  aws dynamodb describe-table --table-name prod-sessions\n  aws dynamodb describe-continuous-backups --table-name prod-sessions\n  aws dynamodb describe-time-to-live --table-name prod-sessions\n  aws kms describe-key --key-id alias\u002Fprod-dynamodb-key\n```\n\n## Decision tree: on-demand vs provisioned\n\n```text\nIs the workload new \u002F unknown traffic pattern?\n├── YES → PAY_PER_REQUEST (on-demand)\n│         (No capacity planning; switch to PROVISIONED after 2-3 weeks\n│          of steady-state traffic data)\n└── NO → Is traffic bursty \u002F unpredictable (> 3:1 peak-to-trough ratio)?\n    ├── YES → PAY_PER_REQUEST (on-demand)\n    │         (Autoscaling has 3-5 min lag; on-demand handles spikes\n    │          instantly within the burst bucket)\n    └── NO → Is traffic steady and high-throughput (> 5,000 RCU\u002FWCU sustained)?\n        ├── YES → PROVISIONED + autoscaling\n        │         (3-5x cheaper than on-demand at sustained load)\n        └── NO → Is the table idle most of the time (dev \u002F test \u002F low-traffic)?\n            ├── YES → PAY_PER_REQUEST (on-demand)\n            │         (Pay zero when idle; provisioned has minimum charges)\n            └── NO → PROVISIONED + autoscaling\n                      (Moderate steady traffic; autoscaling handles\n                       gradual changes)\n```\n\n**Post-decision review:** after 2-3 weeks of production traffic, review\nCloudWatch `ConsumedReadCapacityUnits` \u002F `ConsumedWriteCapacityUnits`. If\nutilization is > 70% steady, PROVISIONED is cheaper. If utilization is\n\u003C 30% or highly bursty, stay on-demand. DynamoDB enforces a cooldown\nbetween mode switches — do not switch per-request.\n\n## Error handling\n\nAll four error-handling deep dives (ResourceInUseException, GSI backfill failure, PITR enable failures, autoscaling registration failures) moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand when a provisioning API call fails.\n\n## Worked example — provisioned table with GSI + autoscaling\n\nFull provisioned-with-GSI worked example (create-table with GSI, 4x autoscaling registration, PITR\u002FTTL\u002FStreams, checklist) moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md); the session-store example above is the primary inline example.\nLoad on demand when provisioning a PROVISIONED table with GSIs.\n\n## Recent AWS features (2024-2026)\n\nRecent AWS features 2024-2026 (zero-ETL integrations, replication enhancements, resource-based policies, table classes, incremental export, deletion protection GA) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when a 2024-2026 feature affects provisioning choices.\n\n## References (load on demand)\n\n- [`references\u002Fadvanced-patterns.md`](references\u002Fadvanced-patterns.md) — Mindset, reasoning framework, dependency graph, three expert heuristics, Step 10 newer features, and recent AWS features (2024-2026) moved from SKILL.md\n- [`references\u002Fprovisioning-cli-commands.md`](references\u002Fprovisioning-cli-commands.md) — autoscaling \u002F PITR \u002F Streams \u002F table class \u002F deletion-protection CLI moved from SKILL.md, plus the pre-existing provisioning commands\n- [`references\u002Ferror-handling.md`](references\u002Ferror-handling.md) — error-handling deep dives (ResourceInUseException, GSI backfill, PITR, autoscaling registration) moved from SKILL.md\n- [`references\u002Fworked-examples.md`](references\u002Fworked-examples.md) — the provisioned-table-with-GSI worked example moved from SKILL.md; the session-store example stays inline\n- [`references\u002Fkey-design-and-capacity.md`](references\u002Fkey-design-and-capacity.md) — pre-existing key-design and capacity reference\n\n## Domain\n\nAWS CloudOps \u002F DynamoDB Table Provisioning & Schema Design.\n\n## AWS documentation\n\n- **Amazon DynamoDB Developer Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FIntroduction.html\n- **DynamoDB Tables, Items, and Attributes** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FHowItWorks.CoreComponents.html\n- **Best Practices for Designing and Using Partition Keys Effectively** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002Fbp-partition-key-design.html\n- **Global Secondary Indexes** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FGSI.html\n- **DynamoDB Streams** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FStreams.html\n- **Point-in-Time Recovery** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FPointInTimeRecovery.html\n- **DynamoDB Table Classes** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002Fddn-table-classes.html\n- **Aurora zero-ETL integration with DynamoDB** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FAuroraUserGuide\u002FConcepts.Aurora_DynamoDB_Integration.html\n","# DynamoDB Table Deployer\n\nAn AWS CloudOps agent skill that provisions DynamoDB tables with correct\ndefaults. The skill walks the operator through a 10-step provisioning\nprocedure, captures the operator's access-pattern decisions (partition key,\nsort key, GSI projections, capacity mode), explains why each default matters,\nand emits a READY_TO_DEPLOY checklist with copy-pasteable verification\ncommands.\n\n## Activation keywords\n\ncreate DynamoDB table, provision DynamoDB, DynamoDB deployment, partition key\ndesign, sort key design, hot partition, random suffix, composite key, GSI\ndesign, sparse index, ALL projection, KEYS_ONLY projection, INCLUDE\nprojection, on-demand capacity, provisioned capacity, PAY_PER_REQUEST,\nautoscaling, PITR, point-in-time recovery, SSE-KMS, customer-managed CMK,\nDynamoDB TTL, item expiration, DynamoDB Streams, NEW_AND_OLD_IMAGES,\nCDC pipeline, table class, Standard-IA, deletion protection, global tables,\nAurora zero-ETL, OpenSearch zero-ETL, resource-based policy.\n\n## Invocation contract (hard requirement)\n\nWhen this skill is invoked with a table-provisioning request (table name,\naccess pattern, workload shape, region, or a partial configuration), the\nagent MUST respond with the READY_TO_DEPLOY checklist defined in\n§\"Output format\" using the literal all-caps labels `TABLE:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the checklist\nwith prose, headings, or disclaimers — emit the block as the first lines\nof the response. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels breaks\nautomation silently.\n\n## Mindset\n\nThree provisioning misconceptions (natural-key hot partitions, on-demand burst bucket, GSI cost cascade) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when explaining why creation-time decisions matter.\n\n## Reasoning framework (why provisioning order matters)\n\nSix ordering rules (key schema before first write, LSI creation-only, capacity mode before traffic, GSI autoscaling at creation, SSE-KMS before first write, additive settings early) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when sequencing the provisioning run.\n\n## DynamoDB configuration dependency graph (novel heuristic)\n\nConfiguration dependency graph (13-row immutability\u002Fsilent-failure matrix plus cross-dependency gotchas) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when a configuration interaction is unclear.\n\n## Expert heuristic: partition key cardinality calculator\n\nPartition key cardinality calculator (10,000-distinct-values rule, quick-check formula, common scenarios) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when sizing a write-heavy partition key.\n\n## Expert heuristic: GSI cost multiplier\n\nGSI cost multiplier (ceil(item_size_kb) x gsi_count, 12-WCU worked example, 30%-of-bill budget heuristic) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand before adding the 3rd GSI.\n\n## Expert heuristic: adaptive capacity false sense of security\n\nAdaptive capacity deep dive (~30-second borrow window, what it does NOT do, throttling signature, on-demand burst bucket) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when throttling appears despite adequate capacity.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If any\nare missing, the verdict is **PREREQUISITES_MISSING** with a specific gap\ncitation.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| AWS account with DynamoDB access | Can't provision without it | `aws sts get-caller-identity` |\n| Region selected | Capacity, KMS, and Streams are region-scoped | `aws configure get region` |\n| Table name available and unique in this region (and globally if Global Tables planned) | Names are region-unique; Global Tables require unique name across all replica regions | `aws dynamodb describe-table --table-name \u003Cname>` returns `ResourceNotFoundException` |\n| KMS key ARN (if SSE-KMS with customer CMK) | Custom encryption requires a CMK in the same region with a key policy granting DynamoDB | `aws kms describe-key --key-id \u003Ccmk-id>` |\n| Access-pattern description | Key schema, sort key, and GSI design are access-pattern-driven and immutable | Captured in the prompt or follow-up question |\n| CMK key policy grants DynamoDB service + calling principal | SSE-KMS requires `kms:GenerateDataKey` + `kms:Decrypt` grants | `aws kms get-key-policy --key-id \u003Ccmk-id> --policy-name default` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING` and\ncite the specific gap.\n\n## 10-step provisioning procedure\n\n### Step 1 — Partition key design (immutable — decide BEFORE create-table)\n\nThe partition key determines how writes distribute across physical\npartitions. A bad partition key is the single highest-impact DynamoDB\ndesign mistake and is **immutable** after creation.\n\n**Decision tree:**\n\n- **High-cardinality, even-distribution workload** (session store, ad-tech\n  events, IoT telemetry, user-profile keying by `userId`): use the natural\n  high-cardinality attribute directly. Verify with a histogram of the\n  attribute if possible.\n\n- **Monotonically increasing attribute as the natural key** (timestamp,\n  auto-increment id, sequential orderId): append a **random suffix** (e.g.,\n  0-99 or a hash bucket) and use `\u003CnaturalKey>#\u003Csuffix>` as the partition\n  key. Distributes writes across N buckets → N physical partitions.\n\n  ```text\n  orderId: 100001  →  partition key: \"100001#37\"\n  orderId: 100002  →  partition key: \"100002#04\"\n  orderId: 100003  →  partition key: \"100003#71\"\n  ```\n\n  The application generates the suffix (random or hash of an unrelated\n  attribute); reads must fan out across all suffixes if the natural key\n  must be reconstructed. This is the canonical fix for hot-partition\n  write throttling.\n\n- **Composite key for hierarchical data** (multi-tenant, time-bucketed):\n  combine tenantId + bucketId into the partition key (e.g.,\n  `\u003CtenantId>#\u003Cyyyy-mm>`), use a sort key for the intra-bucket ordering.\n  Distributes tenants across partitions while keeping tenant data\n  co-located for efficient queries.\n\n- **Low-cardinality attribute (status, category, boolean)**: NEVER use as\n  the partition key alone — writes will concentrate on 1-few partitions.\n  Combine with a high-cardinality attribute to form a composite key.\n\n**Why decided at creation**: the partition key is part of `KeySchema` in\n`create-table` and is immutable. Re-keying an existing table means\ncreate-new → backfill (with re-partitioning) → cutover. Decide before the\nfirst write.\n\n**Common mistake**: using a timestamp-prefix partition key for time-series\ndata. All writes in the current second\u002Fminute\u002Fhour hit one partition\n(DynamoDB hashes the partition key, but a low-cardinality timestamp prefix\nstill concentrates writes within a time bucket). Use the random-suffix\npattern OR use the sort key for time within a high-cardinality partition.\n\n### Step 2 — Sort key design (immutable — decide BEFORE create-table)\n\nThe sort key enables range queries (`between`, `begins_with`) within a\npartition. Decide at creation; sort key is immutable.\n\n**Decision tree:**\n\n- **Time-range queries within an entity** (orders for a user, events for\n  a session, messages in a thread): partition key = entity id, sort key =\n  timestamp (ISO 8601 or epoch). Enables `Query` with\n  `KeyConditionExpression: pk = :entity AND sk BETWEEN :start AND :end`.\n\n- **Hierarchical data** (category\u002Fsubcategory paths, file paths): sort key\n  = path (e.g., `category\u002Fsubcategory\u002Fitem`). Enables `begins_with`\n  queries for subtree retrieval.\n\n- **Latest-item lookup** (leaderboards, current state): use a sort key that\n  sorts newest-first. For numeric\u002Fepoch sort keys, store the negation or\n  `MAX_VALUE - timestamp` so the latest sorts first.\n\n- **No range-query need**: omit the sort key (table can have partition key\n  only). Adding a sort key later requires re-creating the table.\n\n**Common mistake**: planning to use a non-key attribute for range queries\npost-creation. Either (a) add it as the sort key now (immutable), (b) add\nan LSI now (immutable, only-at-creation, 5-per-table limit), or (c) add a\nGSI later (mutable but with capacity\u002Fcascade implications).\n\n### Step 3 — Local Secondary Indexes (LSI) — decide NOW or forever hold peace\n\nLSIs enable range queries on a non-key sort attribute within the SAME\npartition key as the base table. They can ONLY be created at `create-table`\ntime — there is NO API to add an LSI later.\n\n**Hard limits** (do not exceed):\n- 5 LSIs per table (HARD API-enforced limit — cannot be raised via support ticket).\n- 10 GB per-partition size limit on indexed data (silently rejects writes past this point — must monitor per-partition index size).\n\n**When to provision an LSI at creation:**\n- Workload needs strong consistency on the alternate sort attribute (LSI\n  supports eventually-consistent AND strongly-consistent reads; GSI only\n  eventually-consistent).\n- Workload needs range queries within the base table's partition key on a\n  different sort attribute.\n\n**When to defer to a GSI (added later):**\n- The alternate access pattern uses a DIFFERENT partition key (LSI shares\n  the base partition key).\n- Eventual consistency is acceptable.\n- You are unsure — GSIs are reversible; LSIs are not.\n\n**Common mistake**: deciding to \"add the LSI later.\" There is no later.\nIf the workload MIGHT need range queries on a non-key attribute, decide\nat creation. Document the decision in the checklist.\n\n### Step 4 — Global Secondary Indexes (GSI) — design at provisioning\n\nGSIs enable alternate access patterns with a different partition key. They\nCAN be added post-creation, but each GSI has its own capacity, its own\nthrottle cascade back to the base table, and counts toward the 20-per-table\nsoft quota.\n\n**Projection type decision (drives storage cost + write amplification):**\n\n| Projection | What it stores | Write cost | Storage cost | Use when |\n|---|---|---|---|---|\n| `ALL` | Entire base-table item | highest (every base write replicates fully) | highest | GSI is read-heavy and you want to avoid a follow-up GetItem |\n| `INCLUDE` | Keys + specified non-key attributes | medium (only listed attributes projected) | medium | GSI needs a few specific attributes (e.g., status, name) |\n| `KEYS_ONLY` | Only the GSI's key attributes | lowest (minimum replication) | lowest | GSI is a lookup index; follow up with GetItem from the base table for full data |\n\n**Sparse index pattern**: a GSI where the sort key attribute only exists\non SOME items becomes a sparse index — only items with that attribute\nappear in the GSI. Powerful for \"find all items in state X\" queries\nwithout scanning the whole table.\n\n**Capacity per GSI (PROVISIONED mode)**: each GSI has its OWN RCU\u002FWCU\nallocation. A GSI with insufficient WCU throttles BASE TABLE writes —\nthe cascade rule. Always register autoscaling on every GSI in PROVISIONED\nmode (Step 5).\n\n**Quota check**: the 20-GSI-per-table soft limit can be raised via support\nticket. The 5-LSI limit cannot. Plan GSI count at provisioning.\n\n**Common mistake**: provisioning a GSI with `ALL` projection \"for\nconvenience.\" Every base-table write now fully replicates to the GSI,\ndoubling write cost. Default to `KEYS_ONLY` and follow up with a `GetItem`;\nupgrade to `INCLUDE` only for known hot attributes.\n\n### Step 5 — Capacity mode + autoscaling\n\nChoose between `PAY_PER_REQUEST` (on-demand) and `PROVISIONED` with\nautoscaling based on the **traffic profile**, not on a desire to avoid\ncapacity planning.\n\n**Decision matrix:**\n\n| Traffic profile | Recommended mode | Why |\n|---|---|---|\n| Unknown \u002F new workload | `PAY_PER_REQUEST` (on-demand) | No capacity planning needed; pay per request |\n| Bursty \u002F unpredictable | `PAY_PER_REQUEST` (on-demand) | Autoscaling has 3-5 min lag; on-demand handles spikes (within burst bucket) |\n| Steady high-throughput | `PROVISIONED` + autoscaling | 3-5x cheaper than on-demand at sustained load |\n| Idle \u002F dev \u002F test | `PAY_PER_REQUEST` (on-demand) | Pay zero when table is idle; provisioned has minimum capacity charges |\n| Once-per-hour batch | `PAY_PER_REQUEST` (on-demand) | Cold-start burst bucket handles the spike better than provisioned scale-out lag |\n\nOn-demand burst bucket caveat (trailing 30-minute average, empty on cold start) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when on-demand is chosen for bursty traffic.\n\nPROVISIONED autoscaling registration CLI (register-scalable-target + TargetTrackingScaling policies, per-GSI repeat) moved verbatim to [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md).\nLoad on demand when provisioning a PROVISIONED table.\n\n**Common mistake**: registering autoscaling on the base table but NOT on\na GSI. The GSI throttles and cascades back to the base table — the most\ncommonly missed capacity misconfiguration.\n\n**Switching modes**: DynamoDB enforces a cooldown between\nPAY_PER_REQUEST ↔ PROVISIONED switches. Don't switch per-request.\n\n### Step 6 — Encryption (SSE-KMS)\n\nDynamoDB ALWAYS encrypts at rest. The decision is whether to use\nAWS-managed or customer-controlled encryption:\n\n| Option | SSEType | Key policy control | CloudTrail visibility | Use when |\n|---|---|---|---|---|\n| Default (AWS-owned key) | `AES256` | none | none | dev \u002F test \u002F non-compliance workloads |\n| AWS-managed KMS key (`alias\u002Faws\u002Fdynamodb`) | `KMS` | limited (DynamoDB-managed) | partial | when KMS API visibility matters but key policy does not |\n| Customer-managed CMK | `KMS` with explicit `KMSMasterKeyArn` | full (you set the policy) | full (per-call Decrypt events) | compliance (PCI-DSS, HIPAA, SOC2), cross-account, regulated data |\n\n**For compliance workloads**, always use a customer-managed CMK and verify\nthe key policy grants `kms:GenerateDataKey` + `kms:Decrypt` to both\n`dynamodb.\u003Cregion>.amazonaws.com` and the calling principal.\n\n```bash\naws dynamodb create-table ... \\\n  --sse-specification Enabled=true,SSEType=KMS,KMSMasterKeyId=arn:aws:kms:\u003Cregion>:\u003Cacct>:key\u002F\u003Ccmk-id>\n```\n\nKMS cost warning (quota sharing vs the dedicated aws\u002Fdynamodb quota) and the Global Tables CMK-per-region requirement moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when provisioning SSE-KMS at high throughput or multi-region.\n\n### Step 7 — Point-in-time recovery (PITR) — enable by default\n\nPITR enablement CLI, new-table restore semantics, and cost note moved verbatim to [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md).\nLoad on demand when enabling PITR.\n\n### Step 8 — TTL configuration (optional — automatic item expiration)\n\nTTL automatically deletes items whose specified attribute (epoch seconds)\nis in the past. Use for: session expiry, log retention, cache eviction,\nGDPR data-retention enforcement (with caveats below).\n\n```bash\naws dynamodb update-time-to-live --table-name \u003Ctable> \\\n  --time-to-live-specification Enabled=true,AttributeName=ttl\n```\n\n**TTL semantics** (do not misrepresent):\n- Items WITHOUT the TTL attribute are NEVER expired.\n- Deletion is by background scanner within **48 hours** of the expiry\n  timestamp. Items remain readable until physically deleted.\n- TTL is a **cost-optimization feature**, NOT a compliance enforcement\n  mechanism. For immediate\u002Fverifiable deletion, the application must\n  explicitly `DeleteItem`.\n\n**Common mistake**: relying on TTL for GDPR immediate-deletion. The 48-hour\nlag and the \"items without attribute are never expired\" rule both break\nthe contract.\n\n### Step 9 — Streams + table class + deletion protection\n\nStreams StreamViewType selection, table class choice, and deletion protection CLI moved verbatim to [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md).\nLoad on demand when configuring Streams, class, or deletion protection.\n\n### Step 10 — Resource-based policy + Global Tables (newer features)\n\nResource-based policy JSON, Global Tables v2 creation CLI, and the 2024-2026 integration notes (OpenSearch zero-ETL, Aurora zero-ETL, replication metrics) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when provisioning cross-account or multi-region tables.\n\n## NEVER do these things\n\n1. **NEVER pick a partition key without considering cardinality and write\n   distribution.** A monotonically increasing key (timestamp, auto-increment\n   id) creates a hot partition and throttles the table far below its\n   provisioned capacity. Use a random suffix or composite key. Re-keying\n   requires create-new + backfill + cutover.\n\n2. **NEVER plan to \"add the LSI later.\"** Local Secondary Indexes can ONLY\n   be created at `create-table` time. There is NO API to add an LSI\n   post-creation. Decide LSI placement at provisioning or commit to a GSI.\n\n3. **NEVER register autoscaling on the base table but forget the GSIs.**\n   A GSI with insufficient WCU throttles writes to the BASE TABLE — the\n   cascade rule. Register autoscaling on every GSI in PROVISIONED mode.\n\n4. **NEVER use the AWS-managed `alias\u002Faws\u002Fdynamodb` key for compliance\n   workloads (PCI-DSS \u002F HIPAA \u002F SOC2 \u002F FedRAMP).** You cannot customize\n   the key policy. Use a customer-managed CMK with explicit\n   `kms:GenerateDataKey` + `kms:Decrypt` grants.\n\n5. **NEVER rely on TTL for immediate data deletion or GDPR compliance.**\n   TTL items persist for up to 48 hours after expiry. Items without the\n   TTL attribute are never expired. TTL is a cost-optimization feature,\n   not a compliance enforcement mechanism.\n\n6. **NEVER assume on-demand mode eliminates capacity risk.** On-demand\n   has a finite burst bucket derived from the trailing 30 minutes. A\n   cold-start spike from zero can still throttle. Flag this as\n   operational guidance.\n\n7. **NEVER enable Streams as a \"default hardening\" step on tables whose\n   workload does not consume CDC.** Streams incur write-amplification cost\n   and have a 24-hour retention window. Enable Streams only when there is\n   a downstream consumer (Lambda, OpenSearch sync, Kinesis, Aurora zero-ETL).\n\n8. **NEVER exceed the 5-LSI-per-table limit.** It is a HARD API-enforced\n   limit — cannot be raised via support ticket. The 20-GSI soft limit\n   CAN be raised. Plan accordingly at provisioning.\n\n9. **NEVER provision a Global Table replica in a region without the CMK\n   present.** A missing key causes `InaccessibleEncryptionDateTime` —\n   an active outage on that replica. Verify `aws kms describe-key` in\n   every replica region before adding the replica.\n\n10. **NEVER treat `DeletionProtectionEnabled` as a security control.**\n    Any principal with `dynamodb:UpdateTable` can disable it. It is an\n    accidental-deletion \u002F ransomware guardrail, not a defense against a\n    determined attacker with database-admin rights.\n\n11. **NEVER switch billing mode for per-request cost optimization.**\n    DynamoDB enforces a cooldown between `PAY_PER_REQUEST` and `PROVISIONED`\n    switches. Choose based on the sustained traffic profile.\n\n12. **NEVER use `ALL` projection on a GSI \"for convenience.\"** Every\n    base-table write fully replicates, doubling write cost. Default to\n    `KEYS_ONLY` and follow up with a `GetItem`; upgrade to `INCLUDE` for\n    known hot attributes.\n\n## Output format\n\n```text\nTABLE: \u003Ctable-name>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Partition key: \u003Cattribute> (\u003Ctype>) — \u003Cdesign rationale>\n  [✓|✗] Sort key: \u003Cattribute> (\u003Ctype>) | None\n  [✓|✗] LSIs: \u003Clist with sort attributes> | None (5-max HARD limit respected)\n  [✓|✗] GSIs: \u003Clist with projection types> | None\n  [✓|✗] Capacity mode: PAY_PER_REQUEST | PROVISIONED (autoscaling: table ✓ \u003Cgsi> ✓)\n  [✓|✗] Encryption: SSE-KMS customer CMK (\u003Ckey-arn>) | AWS-managed (alias\u002Faws\u002Fdynamodb) | AES256\n  [✓|✗] PITR: Enabled (35-day window)\n  [✓|✗] TTL: Enabled (attribute: \u003Cname>) | Disabled\n  [✓|✗] Streams: NEW_AND_OLD_IMAGES | KEYS_ONLY | NEW_IMAGE | OLD_IMAGE | Disabled\n  [✓|✗] Table class: STANDARD | STANDARD_INFREQUENT_ACCESS\n  [✓|✗] Deletion protection: Enabled | Disabled\n  [✓|✗] Resource-based policy: \u003Csummary> | None\n  [✓|✗] Global Tables: replicas in \u003Cregions> | Single-region\nVERIFICATION_COMMANDS:\n  aws dynamodb describe-table --table-name \u003Ctable>\n  aws dynamodb describe-continuous-backups --table-name \u003Ctable>\n  aws dynamodb describe-time-to-live --table-name \u003Ctable>\n  aws dynamodb describe-kinesis-destination --table-name \u003Ctable>   # if Kinesis fan-out\n  aws application-autoscaling describe-scaling-policies --service-namespace dynamodb\n  aws kms describe-key --key-id \u003Ccmk-id>\n```\n\n### Worked example — high-throughput session store\n\n```text\nTABLE: prod-sessions\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Partition key: sessionId (String) — UUID v4, high-cardinality for even write distribution\n  [✓] Sort key: None (single-item lookup pattern)\n  [✓] LSIs: None (no range-query requirement on alternate sort attribute)\n  [✓] GSIs: gsi_by_userId (userId→sessionId, KEYS_ONLY projection, sparse — only items with userId)\n  [✓] Capacity mode: PAY_PER_REQUEST (bursty session traffic, unpredictable peaks)\n  [✓] Encryption: SSE-KMS customer CMK (alias\u002Fprod-dynamodb-key)\n  [✓] PITR: Enabled (35-day window)\n  [✓] TTL: Enabled (attribute: expiresAt — session token expiry, ~48h lag acceptable)\n  [✓] Streams: NEW_AND_OLD_IMAGES (downstream Lambda publishes session-change events)\n  [✓] Table class: STANDARD (frequently accessed)\n  [✓] Deletion protection: Enabled\n  [✓] Resource-based policy: Allow read-only from analytics account 222222222222\n  [✓] Global Tables: Single-region (us-east-1)\nVERIFICATION_COMMANDS:\n  aws dynamodb describe-table --table-name prod-sessions\n  aws dynamodb describe-continuous-backups --table-name prod-sessions\n  aws dynamodb describe-time-to-live --table-name prod-sessions\n  aws kms describe-key --key-id alias\u002Fprod-dynamodb-key\n```\n\n## Decision tree: on-demand vs provisioned\n\n```text\nIs the workload new \u002F unknown traffic pattern?\n├── YES → PAY_PER_REQUEST (on-demand)\n│         (No capacity planning; switch to PROVISIONED after 2-3 weeks\n│          of steady-state traffic data)\n└── NO → Is traffic bursty \u002F unpredictable (> 3:1 peak-to-trough ratio)?\n    ├── YES → PAY_PER_REQUEST (on-demand)\n    │         (Autoscaling has 3-5 min lag; on-demand handles spikes\n    │          instantly within the burst bucket)\n    └── NO → Is traffic steady and high-throughput (> 5,000 RCU\u002FWCU sustained)?\n        ├── YES → PROVISIONED + autoscaling\n        │         (3-5x cheaper than on-demand at sustained load)\n        └── NO → Is the table idle most of the time (dev \u002F test \u002F low-traffic)?\n            ├── YES → PAY_PER_REQUEST (on-demand)\n            │         (Pay zero when idle; provisioned has minimum charges)\n            └── NO → PROVISIONED + autoscaling\n                      (Moderate steady traffic; autoscaling handles\n                       gradual changes)\n```\n\n**Post-decision review:** after 2-3 weeks of production traffic, review\nCloudWatch `ConsumedReadCapacityUnits` \u002F `ConsumedWriteCapacityUnits`. If\nutilization is > 70% steady, PROVISIONED is cheaper. If utilization is\n\u003C 30% or highly bursty, stay on-demand. DynamoDB enforces a cooldown\nbetween mode switches — do not switch per-request.\n\n## Error handling\n\nAll four error-handling deep dives (ResourceInUseException, GSI backfill failure, PITR enable failures, autoscaling registration failures) moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\nLoad on demand when a provisioning API call fails.\n\n## Worked example — provisioned table with GSI + autoscaling\n\nFull provisioned-with-GSI worked example (create-table with GSI, 4x autoscaling registration, PITR\u002FTTL\u002FStreams, checklist) moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md); the session-store example above is the primary inline example.\nLoad on demand when provisioning a PROVISIONED table with GSIs.\n\n## Recent AWS features (2024-2026)\n\nRecent AWS features 2024-2026 (zero-ETL integrations, replication enhancements, resource-based policies, table classes, incremental export, deletion protection GA) moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\nLoad on demand when a 2024-2026 feature affects provisioning choices.\n\n## References (load on demand)\n\n- [`references\u002Fadvanced-patterns.md`](references\u002Fadvanced-patterns.md) — Mindset, reasoning framework, dependency graph, three expert heuristics, Step 10 newer features, and recent AWS features (2024-2026) moved from SKILL.md\n- [`references\u002Fprovisioning-cli-commands.md`](references\u002Fprovisioning-cli-commands.md) — autoscaling \u002F PITR \u002F Streams \u002F table class \u002F deletion-protection CLI moved from SKILL.md, plus the pre-existing provisioning commands\n- [`references\u002Ferror-handling.md`](references\u002Ferror-handling.md) — error-handling deep dives (ResourceInUseException, GSI backfill, PITR, autoscaling registration) moved from SKILL.md\n- [`references\u002Fworked-examples.md`](references\u002Fworked-examples.md) — the provisioned-table-with-GSI worked example moved from SKILL.md; the session-store example stays inline\n- [`references\u002Fkey-design-and-capacity.md`](references\u002Fkey-design-and-capacity.md) — pre-existing key-design and capacity reference\n\n## Domain\n\nAWS CloudOps \u002F DynamoDB Table Provisioning & Schema Design.\n\n## AWS documentation\n\n- **Amazon DynamoDB Developer Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FIntroduction.html\n- **DynamoDB Tables, Items, and Attributes** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FHowItWorks.CoreComponents.html\n- **Best Practices for Designing and Using Partition Keys Effectively** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002Fbp-partition-key-design.html\n- **Global Secondary Indexes** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FGSI.html\n- **DynamoDB Streams** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FStreams.html\n- **Point-in-Time Recovery** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FPointInTimeRecovery.html\n- **DynamoDB Table Classes** — https:\u002F\u002Fdocs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002Fddn-table-classes.html\n- **Aurora zero-ETL integration with DynamoDB** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FAuroraUserGuide\u002FConcepts.Aurora_DynamoDB_Integration.html\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"dependencies":37,"requires_llm":38,"verdict_shape":39,"lifecycle_status":40,"supports_pipeline":38},"aws, dynamodb, cloudops, deploy, databases, provisioning, partition-key, gsi, pitr, sse-kms, ttl, streams, deletion-protection","1","Jacky Chan — AWS Community Builder","aws-cloudops","Databases","0.1.0","aws, dynamodb, cloudops, deploy, provisioning, partition key, sort key, gsi, global secondary index, lsi, on-demand, provisioned, pay per request, autoscaling, pitr, point-in-time recovery, sse-kms, ttl, time to live, dynamodb streams, cdc, table class, standard-ia, deletion protection, global tables, zero-etl, aurora zero-etl, opensearch zero-etl","deploy","high","false","capability","Invoke when the user wants to create a new DynamoDB table with production defaults, design a partition\u002Fsort key scheme, plan GSI access patterns, harden an existing table before production, validate key\u002Fschema design before go-live, plan CDC pipelines via DynamoDB Streams, set up global tables, or generate provisioning CLI commands \u002F IaC templates. Do NOT invoke for auditing existing table posture (use dynamodb-table-auditor), or for non-DynamoDB NoSQL (DocumentDB, ElastiCache, Neptune, Timestream).","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","experimental","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with dynamodb, application- autoscaling, kms, and iam access. Works with Terraform aws_dynamodb_table resources and CloudFormation AWS::DynamoDB::Table templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fdynamodb-table-deployer",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill dynamodb-table-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill dynamodb-table-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill dynamodb-table-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6808,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fad-tech-event-ingest.md",1760,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fbaselines\u002Fad-tech-event-ingest.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fcompliance-audit-log-table.md",1274,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fbaselines\u002Fcompliance-audit-log-table.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fcost-optimized-ia-table.md",1179,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fbaselines\u002Fcost-optimized-ia-table.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fhigh-throughput-session-store.md",1886,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fbaselines\u002Fhigh-throughput-session-store.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fmissing-cmk-and-key-schema.md",1087,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fbaselines\u002Fmissing-cmk-and-key-schema.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1791,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",13215,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fad-tech-event-ingest.md",839,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fprompts\u002Fad-tech-event-ingest.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fcompliance-audit-log-table.md",778,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fprompts\u002Fcompliance-audit-log-table.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fcost-optimized-ia-table.md",641,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fprompts\u002Fcost-optimized-ia-table.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fhigh-throughput-session-store.md",774,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fprompts\u002Fhigh-throughput-session-store.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fmissing-cmk-and-key-schema.md",395,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fevals\u002Fprompts\u002Fmissing-cmk-and-key-schema.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",7305,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",16359,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Ferror-handling.md",3062,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Freferences\u002Ferror-handling.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fkey-design-and-capacity.md",11487,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Freferences\u002Fkey-design-and-capacity.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fprovisioning-cli-commands.md",15056,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Freferences\u002Fprovisioning-cli-commands.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fworked-examples.md",6863,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Freferences\u002Fworked-examples.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4417,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdynamodb-table-deployer\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]