@raishin/vanguard-frontier-agentic 3.19.0 → 3.20.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +2 -2
- package/.claude-plugin/plugin.json +8 -1
- package/.cursor-plugin/plugin.json +8 -1
- package/.github/plugin/marketplace.json +1 -1
- package/README.md +21 -21
- package/agents/AGENTS.md +4 -4
- package/agents/README.md +7 -7
- package/agents/alibaba/alibaba-tablestore-architect-agent/AGENT.md +54 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/codex.toml +11 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/metadata.json +39 -0
- package/agents/aws/aws-dynamodb-patterns-agent/AGENT.md +53 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/codex.toml +23 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/copilot.agent.md +42 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/cursor.agent.md +38 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/gemini.agent.md +38 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/aws/aws-dynamodb-patterns-agent/metadata.json +39 -0
- package/agents/azure/azure-cosmosdb-application-developer-agent/metadata.json +4 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/AGENT.md +53 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/codex.toml +23 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/copilot.agent.md +42 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/cursor.agent.md +37 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/gemini.agent.md +38 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/metadata.json +38 -0
- package/agents/gcp/gcp-bigtable-architect-agent/AGENT.md +54 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/codex.toml +11 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/gcp/gcp-bigtable-architect-agent/metadata.json +39 -0
- package/agents/huawei/huawei-geminidb-architect-agent/AGENT.md +54 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/codex.toml +11 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/huawei/huawei-geminidb-architect-agent/metadata.json +38 -0
- package/agents/oci/oci-nosql-database-architect-agent/AGENT.md +54 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/codex.toml +11 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/cursor.agent.md +39 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/oci/oci-nosql-database-architect-agent/metadata.json +39 -0
- package/agents/oci/oci-nosql-pattern-agent/AGENT.md +53 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/codex.toml +23 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/copilot.agent.md +42 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/cursor.agent.md +38 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/gemini.agent.md +38 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/oci/oci-nosql-pattern-agent/metadata.json +38 -0
- package/catalog/agents.json +204 -1
- package/catalog/asset-integrity.json +601 -61
- package/catalog/install-roles.json +19 -1
- package/catalog/model-assignments.json +231 -0
- package/catalog/skill-manifest.json +1603 -56
- package/catalog/skills.json +314 -14
- package/package.json +7 -2
- package/plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json +1 -1
- package/powers/vanguard-alibaba/POWER.md +1 -1
- package/powers/vanguard-aws/POWER.md +1 -1
- package/powers/vanguard-azure/POWER.md +1 -1
- package/powers/vanguard-gcp/POWER.md +1 -1
- package/powers/vanguard-huawei/POWER.md +1 -1
- package/powers/vanguard-oci/POWER.md +1 -1
- package/skills/alibaba/README.md +2 -1
- package/skills/alibaba/alibaba-maestro/SKILL.md +2 -1
- package/skills/alibaba/alibaba-tablestore-architect/SKILL.md +69 -0
- package/skills/alibaba/alibaba-tablestore-architect/metadata.json +28 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/live.md +110 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/offline.md +119 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit.md +22 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/evidence-ledger.md +87 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/operations.md +190 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/tablestore-design-guide.md +159 -0
- package/skills/aws/aws-documentdb-architect/SKILL.md +43 -0
- package/skills/aws/aws-documentdb-architect/metadata.json +26 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit/live.md +135 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit/offline.md +127 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit.md +23 -0
- package/skills/aws/aws-documentdb-architect/references/evidence-ledger.md +52 -0
- package/skills/aws/aws-documentdb-architect/references/official-sources.md +15 -0
- package/skills/aws/aws-documentdb-architect/references/operations.md +165 -0
- package/skills/aws/aws-documentdb-architect/references/safety-checklist.md +22 -0
- package/skills/aws/aws-documentdb-architect/references/workflow-and-output.md +22 -0
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/SKILL.md +5 -3
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/metadata.json +7 -3
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/consistency-indexing-replication.md +103 -0
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/evidence-ledger.md +38 -0
- package/skills/aws/aws-dynamodb-patterns/CHANGELOG.md +87 -0
- package/skills/aws/aws-dynamodb-patterns/README.md +132 -0
- package/skills/aws/aws-dynamodb-patterns/SKILL.md +82 -0
- package/skills/aws/aws-dynamodb-patterns/assets/bedrock-embedding-input.json +6 -0
- package/skills/aws/aws-dynamodb-patterns/assets/content-review.json +6 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table-with-lsi.json +41 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table.json +27 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table.sh +37 -0
- package/skills/aws/aws-dynamodb-patterns/assets/embedding-flow.py +89 -0
- package/skills/aws/aws-dynamodb-patterns/assets/query-input.json +13 -0
- package/skills/aws/aws-dynamodb-patterns/assets/query-pages.mjs +54 -0
- package/skills/aws/aws-dynamodb-patterns/assets/stream-read-policy.json +11 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table-index-read-policy.json +20 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table-resource-policy.json +22 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table.cfn.yaml +55 -0
- package/skills/aws/aws-dynamodb-patterns/assets/typed-vector-item.json +15 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-create-table.json +23 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-search-policy.json +11 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-search.json +10 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-table.cfn.yaml +41 -0
- package/skills/aws/aws-dynamodb-patterns/evals/audit.test.py +87 -0
- package/skills/aws/aws-dynamodb-patterns/evals/backup-restore.test.py +163 -0
- package/skills/aws/aws-dynamodb-patterns/evals/commands.test.py +185 -0
- package/skills/aws/aws-dynamodb-patterns/evals/create-table.test.py +99 -0
- package/skills/aws/aws-dynamodb-patterns/evals/data-vectors-maintenance.test.py +201 -0
- package/skills/aws/aws-dynamodb-patterns/evals/embedding-commands.test.py +162 -0
- package/skills/aws/aws-dynamodb-patterns/evals/embedding-flow.test.py +167 -0
- package/skills/aws/aws-dynamodb-patterns/evals/eval.md +328 -0
- package/skills/aws/aws-dynamodb-patterns/evals/evals.json +185 -0
- package/skills/aws/aws-dynamodb-patterns/evals/modes.test.py +195 -0
- package/skills/aws/aws-dynamodb-patterns/evals/operations.test.py +288 -0
- package/skills/aws/aws-dynamodb-patterns/evals/query-pages.test.mjs +156 -0
- package/skills/aws/aws-dynamodb-patterns/evals/readme-and-loading.test.py +69 -0
- package/skills/aws/aws-dynamodb-patterns/evals/verify.py +166 -0
- package/skills/aws/aws-dynamodb-patterns/metadata.json +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/README.md +32 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit/live.md +64 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit/offline.md +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit.md +65 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/aws-cli.md +206 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup/on-demand.md +36 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup/pitr.md +41 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup.md +27 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/design.md +47 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/embedding.md +200 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/feature-plan.md +56 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/help.md +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/performance-test.md +95 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/recovery-target.md +47 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/refactor.md +82 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore/on-demand.md +32 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore/pitr.md +42 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore.md +76 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/select.md +22 -0
- package/skills/aws/aws-dynamodb-patterns/references/data-types-and-vectors.md +175 -0
- package/skills/aws/aws-dynamodb-patterns/references/embedding-integrations.md +237 -0
- package/skills/aws/aws-dynamodb-patterns/references/encryption.md +156 -0
- package/skills/aws/aws-dynamodb-patterns/references/evidence-index.md +116 -0
- package/skills/aws/aws-dynamodb-patterns/references/evidence-ledger.md +373 -0
- package/skills/aws/aws-dynamodb-patterns/references/iam-and-access.md +173 -0
- package/skills/aws/aws-dynamodb-patterns/references/language-adapters.md +251 -0
- package/skills/aws/aws-dynamodb-patterns/references/lsi-vs-gsi.md +116 -0
- package/skills/aws/aws-dynamodb-patterns/references/maintenance.md +56 -0
- package/skills/aws/aws-dynamodb-patterns/references/modeling.md +131 -0
- package/skills/aws/aws-dynamodb-patterns/references/monitoring.md +137 -0
- package/skills/aws/aws-dynamodb-patterns/references/official-sources.md +34 -0
- package/skills/aws/aws-dynamodb-patterns/references/operations.md +130 -0
- package/skills/aws/aws-dynamodb-patterns/references/provisioning.md +110 -0
- package/skills/aws/aws-dynamodb-patterns/references/recovery-and-replicas.md +148 -0
- package/skills/aws/aws-dynamodb-patterns/references/runtime-contract.md +140 -0
- package/skills/aws/aws-dynamodb-patterns/references/safety-checklist.md +35 -0
- package/skills/aws/aws-dynamodb-patterns/references/sources.md +170 -0
- package/skills/aws/aws-dynamodb-patterns/references/streams-and-dax.md +160 -0
- package/skills/aws/aws-dynamodb-patterns/references/workflow-and-output.md +34 -0
- package/skills/aws/aws-dynamodb-patterns/references/workflow.md +133 -0
- package/skills/aws/aws-dynamodb-patterns/scripts/review_due.py +61 -0
- package/skills/aws/aws-dynamodb-patterns/scripts/select_mode.py +127 -0
- package/skills/aws/aws-keyspaces-architect/SKILL.md +43 -0
- package/skills/aws/aws-keyspaces-architect/metadata.json +26 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit/live.md +118 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit/offline.md +125 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit.md +22 -0
- package/skills/aws/aws-keyspaces-architect/references/evidence-ledger.md +49 -0
- package/skills/aws/aws-keyspaces-architect/references/official-sources.md +15 -0
- package/skills/aws/aws-keyspaces-architect/references/operations.md +154 -0
- package/skills/aws/aws-keyspaces-architect/references/safety-checklist.md +22 -0
- package/skills/aws/aws-keyspaces-architect/references/workflow-and-output.md +22 -0
- package/skills/aws/aws-maestro/SKILL.md +1 -1
- package/skills/aws/aws-maestro/metadata.json +1 -1
- package/skills/aws/aws-maestro/references/workflow-and-output.md +1 -0
- package/skills/azure/azure-cosmosdb-application-developer/SKILL.md +4 -2
- package/skills/azure/azure-cosmosdb-application-developer/metadata.json +1 -1
- package/skills/azure/azure-cosmosdb-pattern/CHANGELOG.md +10 -0
- package/skills/azure/azure-cosmosdb-pattern/README.md +102 -0
- package/skills/azure/azure-cosmosdb-pattern/SKILL.md +69 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/account.arm.json +59 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/content-review.json +9 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/indexing-policy.json +7 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/order.json +10 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/provision.sh +32 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/runtime.mjs +99 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/vector-indexing-policy.json +7 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/vector-policy.json +3 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/eval.md +32 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/fixtures/recovery-continuous.json +28 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/prompts.json +24 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/report.md +54 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/runtime.test.mjs +146 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/source-evidence.json +28 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/test_package.py +355 -0
- package/skills/azure/azure-cosmosdb-pattern/metadata.json +25 -0
- package/skills/azure/azure-cosmosdb-pattern/references/access-control.md +42 -0
- package/skills/azure/azure-cosmosdb-pattern/references/change-feed-and-integrations.md +31 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/live.md +17 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/offline.md +15 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit.md +8 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/azure-cli.md +39 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/continuous.md +30 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/periodic.md +28 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup.md +11 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/design.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/feature-plan.md +18 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/help.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/performance-test.md +24 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/recovery-target.md +30 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/refactor.md +14 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-deleted-resource.md +55 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-new-account.md +50 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/periodic-support.md +27 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/select.md +11 -0
- package/skills/azure/azure-cosmosdb-pattern/references/data-types-and-vectors.md +51 -0
- package/skills/azure/azure-cosmosdb-pattern/references/embedding-integrations.md +56 -0
- package/skills/azure/azure-cosmosdb-pattern/references/encryption.md +53 -0
- package/skills/azure/azure-cosmosdb-pattern/references/evidence-index.md +72 -0
- package/skills/azure/azure-cosmosdb-pattern/references/evidence-ledger.md +174 -0
- package/skills/azure/azure-cosmosdb-pattern/references/indexing-and-capacity.md +37 -0
- package/skills/azure/azure-cosmosdb-pattern/references/language-adapters.md +112 -0
- package/skills/azure/azure-cosmosdb-pattern/references/maintenance.md +19 -0
- package/skills/azure/azure-cosmosdb-pattern/references/modeling.md +44 -0
- package/skills/azure/azure-cosmosdb-pattern/references/monitoring.md +23 -0
- package/skills/azure/azure-cosmosdb-pattern/references/provisioning.md +61 -0
- package/skills/azure/azure-cosmosdb-pattern/references/recovery.md +31 -0
- package/skills/azure/azure-cosmosdb-pattern/references/replication.md +22 -0
- package/skills/azure/azure-cosmosdb-pattern/references/runtime-contract.md +43 -0
- package/skills/azure/azure-cosmosdb-pattern/references/sources.md +61 -0
- package/skills/azure/azure-cosmosdb-pattern/references/workflow.md +18 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/recovery_guard.py +96 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/review_due.py +26 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/select_mode.py +108 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/validate_assets.py +53 -0
- package/skills/azure/azure-cosmosdb-platform-operator/SKILL.md +6 -2
- package/skills/azure/azure-cosmosdb-platform-operator/metadata.json +6 -3
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/live.md +180 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/offline.md +160 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit.md +26 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/consistency-capacity-security.md +136 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/cosmosdb-platform-operations.md +1 -1
- package/skills/azure/azure-cosmosdb-platform-operator/references/evidence-ledger.md +242 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations-cassandra.md +178 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations-mongodb.md +202 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations.md +126 -0
- package/skills/azure/azure-maestro/SKILL.md +1 -0
- package/skills/gcp/README.md +2 -1
- package/skills/gcp/gcp-bigtable-architect/SKILL.md +71 -0
- package/skills/gcp/gcp-bigtable-architect/metadata.json +28 -0
- package/skills/gcp/gcp-bigtable-architect/references/bigtable-design-guide.md +156 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit/live.md +122 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit/offline.md +140 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit.md +21 -0
- package/skills/gcp/gcp-bigtable-architect/references/evidence-ledger.md +83 -0
- package/skills/gcp/gcp-bigtable-architect/references/operations.md +111 -0
- package/skills/gcp/gcp-firebase-developer/SKILL.md +6 -3
- package/skills/gcp/gcp-firebase-developer/metadata.json +14 -4
- package/skills/gcp/gcp-firebase-developer/references/commands/audit/live.md +124 -0
- package/skills/gcp/gcp-firebase-developer/references/commands/audit/offline.md +146 -0
- package/skills/gcp/gcp-firebase-developer/references/commands/audit.md +27 -0
- package/skills/gcp/gcp-firebase-developer/references/evidence-ledger.md +190 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore-mongodb-operations.md +189 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore-operations.md +202 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore.md +122 -0
- package/skills/gcp/gcp-maestro/SKILL.md +2 -1
- package/skills/huawei/README.md +2 -1
- package/skills/huawei/huawei-gaussdb-rds-dba/SKILL.md +7 -4
- package/skills/huawei/huawei-gaussdb-rds-dba/metadata.json +12 -4
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/live.md +68 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/offline.md +106 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit.md +23 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/dds-operations.md +135 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/evidence-ledger.md +87 -0
- package/skills/huawei/huawei-geminidb-architect/SKILL.md +68 -0
- package/skills/huawei/huawei-geminidb-architect/metadata.json +26 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit/live.md +68 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit/offline.md +108 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit.md +23 -0
- package/skills/huawei/huawei-geminidb-architect/references/evidence-ledger.md +83 -0
- package/skills/huawei/huawei-geminidb-architect/references/geminidb-design-guide.md +114 -0
- package/skills/huawei/huawei-geminidb-architect/references/operations.md +135 -0
- package/skills/huawei/huawei-maestro/SKILL.md +2 -1
- package/skills/ionos/ionos-live-database-lifecycle-guard/SKILL.md +2 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/live.md +87 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/offline.md +109 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit.md +27 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/evidence-ledger.md +69 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/mongodb-operations.md +220 -0
- package/skills/oci/README.md +6 -1
- package/skills/oci/oci-nosql-database-architect/SKILL.md +73 -0
- package/skills/oci/oci-nosql-database-architect/metadata.json +28 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit/live.md +136 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit/offline.md +150 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit.md +28 -0
- package/skills/oci/oci-nosql-database-architect/references/evidence-ledger.md +96 -0
- package/skills/oci/oci-nosql-database-architect/references/nosql-design-guide.md +194 -0
- package/skills/oci/oci-nosql-database-architect/references/operations.md +194 -0
- package/skills/oci/oci-nosql-database-architect/references/sdk-matrix.md +43 -0
- package/skills/oci/oci-nosql-pattern/CHANGELOG.md +8 -0
- package/skills/oci/oci-nosql-pattern/README.md +81 -0
- package/skills/oci/oci-nosql-pattern/SKILL.md +62 -0
- package/skills/oci/oci-nosql-pattern/assets/content-review.json +10 -0
- package/skills/oci/oci-nosql-pattern/assets/create-table.sh +32 -0
- package/skills/oci/oci-nosql-pattern/assets/index-keys.json +11 -0
- package/skills/oci/oci-nosql-pattern/assets/migrator-export.json +22 -0
- package/skills/oci/oci-nosql-pattern/assets/migrator-import.json +29 -0
- package/skills/oci/oci-nosql-pattern/assets/orders.ddl +9 -0
- package/skills/oci/oci-nosql-pattern/assets/orders.tf +46 -0
- package/skills/oci/oci-nosql-pattern/assets/query-pages.mjs +33 -0
- package/skills/oci/oci-nosql-pattern/assets/query.json +13 -0
- package/skills/oci/oci-nosql-pattern/assets/query.sql +1 -0
- package/skills/oci/oci-nosql-pattern/assets/recovery-manifest.example.json +35 -0
- package/skills/oci/oci-nosql-pattern/assets/row.json +10 -0
- package/skills/oci/oci-nosql-pattern/assets/table-limits.json +6 -0
- package/skills/oci/oci-nosql-pattern/evals/cli-shapes.json +222 -0
- package/skills/oci/oci-nosql-pattern/evals/eval.md +26 -0
- package/skills/oci/oci-nosql-pattern/evals/prompts.json +89 -0
- package/skills/oci/oci-nosql-pattern/evals/report.md +41 -0
- package/skills/oci/oci-nosql-pattern/evals/test_package.py +350 -0
- package/skills/oci/oci-nosql-pattern/evals/test_runtime.mjs +77 -0
- package/skills/oci/oci-nosql-pattern/metadata.json +25 -0
- package/skills/oci/oci-nosql-pattern/references/access.md +29 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit/live.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit/offline.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit.md +6 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup/migrator.md +12 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup/sdk.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup.md +7 -0
- package/skills/oci/oci-nosql-pattern/references/commands/design.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/feature-plan.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/help.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/performance-test.md +12 -0
- package/skills/oci/oci-nosql-pattern/references/commands/refactor.md +9 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore/migrator.md +13 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore/sdk.md +11 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/select.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/embedding-integrations.md +25 -0
- package/skills/oci/oci-nosql-pattern/references/encryption.md +18 -0
- package/skills/oci/oci-nosql-pattern/references/evidence-index.md +44 -0
- package/skills/oci/oci-nosql-pattern/references/evidence-ledger.md +73 -0
- package/skills/oci/oci-nosql-pattern/references/indexes.md +19 -0
- package/skills/oci/oci-nosql-pattern/references/language-adapters.md +160 -0
- package/skills/oci/oci-nosql-pattern/references/maintenance.md +15 -0
- package/skills/oci/oci-nosql-pattern/references/modeling.md +26 -0
- package/skills/oci/oci-nosql-pattern/references/monitoring.md +21 -0
- package/skills/oci/oci-nosql-pattern/references/provisioning.md +44 -0
- package/skills/oci/oci-nosql-pattern/references/recovery-boundary.md +32 -0
- package/skills/oci/oci-nosql-pattern/references/replicas.md +18 -0
- package/skills/oci/oci-nosql-pattern/references/runtime-contract.md +23 -0
- package/skills/oci/oci-nosql-pattern/references/sources.md +57 -0
- package/skills/oci/oci-nosql-pattern/references/ttl.md +19 -0
- package/skills/oci/oci-nosql-pattern/references/types-and-vectors.md +27 -0
- package/skills/oci/oci-nosql-pattern/scripts/check_recovery.py +52 -0
- package/skills/oci/oci-nosql-pattern/scripts/review_due.py +32 -0
- package/skills/oci/oci-nosql-pattern/scripts/select_mode.py +96 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/SKILL.md +43 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/metadata.json +25 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/live.md +90 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/offline.md +112 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit.md +24 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/evidence-ledger.md +93 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/official-sources.md +15 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/operations.md +216 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/safety-checklist.md +22 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/workflow-and-output.md +22 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/SKILL.md +43 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/metadata.json +24 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/live.md +99 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/offline.md +114 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit.md +24 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/evidence-ledger.md +43 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/official-sources.md +14 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/operations.md +114 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/safety-checklist.md +22 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/workflow-and-output.md +22 -0
- package/templates/nosql-audit-template.md +127 -0
- package/templates/nosql-operations-template.md +60 -0
- package/tests/_generate_maestro_routing_fixtures.py +11 -0
- package/tests/fixtures/README.md +2 -2
- package/tests/fixtures/alibaba-maestro-routing/expected/050-happy-tablestore-partition-key.json +6 -0
- package/tests/fixtures/alibaba-maestro-routing/expected/adv-tablestore-not-polardb.json +6 -0
- package/tests/fixtures/alibaba-maestro-routing/inputs/050-happy-tablestore-partition-key.json +7 -0
- package/tests/fixtures/alibaba-maestro-routing/inputs/adv-tablestore-not-polardb.json +7 -0
- package/tests/fixtures/alibaba-maestro-routing/taxonomy.json +13 -0
- package/tests/fixtures/aws-maestro-routing/expected/042-happy-dynamodb-patterns.json +6 -0
- package/tests/fixtures/aws-maestro-routing/expected/043-happy-dynamodb-vector-index.json +6 -0
- package/tests/fixtures/aws-maestro-routing/inputs/042-happy-dynamodb-patterns.json +7 -0
- package/tests/fixtures/aws-maestro-routing/inputs/043-happy-dynamodb-vector-index.json +7 -0
- package/tests/fixtures/aws-maestro-routing/taxonomy.json +15 -1
- package/tests/fixtures/azure-maestro-routing/expected/028-happy-cosmosdb-pattern-feature-plan.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/029-happy-cosmosdb-pattern-refactor.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-hot-partition-not-key-vault.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-partition-key-not-key-vault.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-throttling-investigation.json +6 -0
- package/tests/fixtures/azure-maestro-routing/inputs/028-happy-cosmosdb-pattern-feature-plan.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/029-happy-cosmosdb-pattern-refactor.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-hot-partition-not-key-vault.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-partition-key-not-key-vault.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-throttling-investigation.json +7 -0
- package/tests/fixtures/azure-maestro-routing/taxonomy.json +21 -2
- package/tests/fixtures/gcp-maestro-routing/expected/049-happy-bigtable-row-key.json +6 -0
- package/tests/fixtures/gcp-maestro-routing/expected/adv-bigtable-not-firestore.json +8 -0
- package/tests/fixtures/gcp-maestro-routing/inputs/049-happy-bigtable-row-key.json +7 -0
- package/tests/fixtures/gcp-maestro-routing/inputs/adv-bigtable-not-firestore.json +7 -0
- package/tests/fixtures/gcp-maestro-routing/taxonomy.json +15 -0
- package/tests/fixtures/huawei-maestro-routing/expected/050-happy-geminidb-cassandra-partition.json +6 -0
- package/tests/fixtures/huawei-maestro-routing/expected/adv-geminidb-mongo-routes-dds.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/inputs/050-happy-geminidb-cassandra-partition.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/inputs/adv-geminidb-mongo-routes-dds.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/taxonomy.json +15 -0
- package/tests/fixtures/nosql-scenarios/scenarios.json +472 -0
- package/tests/fixtures/oci-maestro-routing/expected/031-happy-nosql-database-architect.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/032-happy-nosql-global-active-table.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/033-happy-nosql-pattern-recovery.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/034-happy-nosql-pattern-refactor.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-live-mutation.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-not-autonomous.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/031-happy-nosql-database-architect.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/032-happy-nosql-global-active-table.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/033-happy-nosql-pattern-recovery.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/034-happy-nosql-pattern-refactor.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-live-mutation.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-not-autonomous.json +7 -0
- package/tests/fixtures/oci-maestro-routing/taxonomy.json +27 -0
- package/tests/requirements-ci.txt +8 -0
- package/tests/validate-aws-skill-quality.py +7 -0
- package/tests/validate-nosql-audit.py +741 -0
- package/tests/validate-nosql-operations.py +136 -0
- package/tests/validate-nosql-pattern-evals.py +96 -0
- package/tests/validate-nosql-scenarios.py +94 -0
- package/tests/validate-skill-manifest.py +6 -1
- package/tests/validate-skill-references.py +225 -0
|
@@ -0,0 +1,373 @@
|
|
|
1
|
+
# Evidence ledger — Amazon DynamoDB patterns
|
|
2
|
+
|
|
3
|
+
Rows trace material AWS claims in this skill to the AWS page that was fetched and
|
|
4
|
+
read on the retrieval date. [The evidence index](evidence-index.md) maps every row to
|
|
5
|
+
the skill files it covers; `tests/validate-skill-references.py` fails the build if a
|
|
6
|
+
citation has no row, a row is never cited, or a source is not an allow-listed host.
|
|
7
|
+
|
|
8
|
+
`VERIFIED` = the cited section was retrieved and supports the claim as worded
|
|
9
|
+
(documentation verification, not a live AWS test). `UNVERIFIED` = no official sentence
|
|
10
|
+
settled it in this pass. `CONFLICT` = two official AWS pages disagree; the skill text
|
|
11
|
+
already warns about the disagreement. Limits and APIs change: re-fetch before relying
|
|
12
|
+
on a number.
|
|
13
|
+
|
|
14
|
+
| ID | Claim | Source | Section | Retrieved | Status |
|
|
15
|
+
| --- | --- | --- | --- | --- | --- |
|
|
16
|
+
| DP-E101 | GSI reads are eventual only; ConsistentRead=true on a GSI is rejected (modeling.md:45; lsi-vs-gsi.md:32-33,104; runtime-contract.md:45,235; workflow.md:202) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | ConsistentRead (Request Parameters): Strongly consistent reads are not supported on global secondary indexes. If you query a global secondary index with `ConsistentRead` set to `true`, you will receive a `ValidationException`. | 2026-11-08 | VERIFIED |
|
|
17
|
+
| DP-E102 | GSI propagation is asynchronous/eventually consistent; queries may be stale (modeling.md:46-47,78-79; lsi-vs-gsi.md:11; runtime-contract.md:130) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.html | Data synchronization between tables and Global Secondary Indexes: your applications need to anticipate and handle situations where a query on a global secondary index returns results that are not up to date. | 2026-11-08 | VERIFIED |
|
|
18
|
+
| DP-E103 | Streams reads are eventual only (table/LSI may be strong) (runtime-contract.md:45) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadConsistency.html | DynamoDB read consistency: Both tables and LSIs provide two read consistency options: eventually consistent (default) and strongly consistent reads. All reads from GSIs and streams are eventually consistent. | 2026-11-08 | VERIFIED |
|
|
19
|
+
| DP-E104 | Sparse GSI: item appears only if index key attributes present; removing both keys removes it (modeling.md:61-62,66; workflow.md:183; lsi-vs-gsi.md:219-220) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-indexes-general-sparse-indexes.html | Take advantage of sparse indexes: DynamoDB writes a corresponding index entry only if the index key attributes are present in the item. | 2026-11-08 | VERIFIED |
|
|
20
|
+
| DP-E105 | Numbers sort numerically only as Number keys; strings sort lexically (modeling.md:86-88) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.html | Multi-attribute key schema: Number attributes sort numerically without requiring zero-padding, while String attributes sort lexicographically. | 2026-11-08 | VERIFIED |
|
|
21
|
+
| DP-E106 | GSI has independently provisioned throughput (provisioned mode); KEYS_ONLY/INCLUDE/ALL projections (modeling.md:92-95; lsi-vs-gsi.md:166) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.html | Provisioned throughput considerations for Global Secondary Indexes; Attribute projections: The provisioned throughput settings of a global secondary index are separate from those of its base table. | 2026-11-08 | VERIFIED |
|
|
22
|
+
| DP-E107 | GSI overload/back-pressure can throttle base-table writes (modeling.md:93,109; lsi-vs-gsi.md:166) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/gsi-throttling.html | Understanding GSI back-pressure throttling: If a GSI doesn't have sufficient capacity to handle these updates, DynamoDB throttles writes to the base table to maintain data consistency. This is called GSI back-pressure. | 2026-11-08 | VERIFIED |
|
|
23
|
+
| DP-E108 | LSI: same PK, alt sort key, 10 GB per item collection (base + all LSI entries) per partition key value; applies only to tables with LSIs (modeling.md:96-99; lsi-vs-gsi.md:12-14,34,165,225; workflow.md:201; design.md:306) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LSI.html | Item collection size limit: The maximum size of any item collection for a table which has one or more local secondary indexes is 10 GB. This does not apply to item collections in tables without local secondary indexes, and also does not apply to it | 2026-11-08 | VERIFIED |
|
|
24
|
+
| DP-E109 | LSIs can only be created with the table; cannot add or delete later (modeling.md:96-97; lsi-vs-gsi.md:33,164,236,214; refactor.md:29) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/SecondaryIndexes.html | Comparison table (Online Index Operations): Local secondary indexes are created at the same time that you create a table. You cannot add a local secondary index to an existing table, nor can you delete any local secondary indexes that currently exist. | 2026-11-08 | VERIFIED |
|
|
25
|
+
| DP-E110 | LSI partition key is exactly the base partition key; GSI can reuse it or use a different attribute (lsi-vs-gsi.md:29) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/SecondaryIndexes.html | Comparison table (Key Attributes) / key schema list: For a global secondary index, the partition key can be any scalar attribute of the base table. | 2026-11-08 | VERIFIED |
|
|
26
|
+
| DP-E111 | LSI requires an alternate sort key (composite key); GSI sort key optional (lsi-vs-gsi.md:30 (first half)) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/SecondaryIndexes.html | Comparison table (Key Schema): The primary key of a local secondary index must be composite (partition key and sort key). | 2026-11-08 | VERIFIED |
|
|
27
|
+
| DP-E112 | "base table must have a sort key" for an LSI (lsi-vs-gsi.md:30 (second half)) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LSI.html | Scenario: Using a Local Secondary Index: Searched LSI.html, SecondaryIndexes.html: no sentence states the base table must have a sort key (only that the base sort key is projected into the LSI). | 2026-11-08 | UNVERIFIED |
|
|
28
|
+
| DP-E113 | LSI supports eventual or strong via ConsistentRead (lsi-vs-gsi.md:32,125) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LSI.html | Querying a Local Secondary Index: You can query a local secondary index using either eventually consistent or strongly consistent reads. | 2026-11-08 | VERIFIED |
|
|
29
|
+
| DP-E114 | GSI can be created with table or added/deleted online; backfill (lsi-vs-gsi.md:33) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.OnlineOps.html | Adding a Global Secondary Index to an existing table: To add a global secondary index to an existing table, use the `UpdateTable` operation with the `GlobalSecondaryIndexUpdates` parameter. | 2026-11-08 | VERIFIED |
|
|
30
|
+
| DP-E115 | LSI reads/writes share the table's provisioned allocation (lsi-vs-gsi.md:35) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/SecondaryIndexes.html | Comparison table (Provisioned Throughput Consumption): Queries or scans on a local secondary index consume read capacity units from the base table. When you write to a table its local secondary indexes are also updated, and these updates consume write capacity units from the | 2026-11-08 | VERIFIED |
|
|
31
|
+
| DP-E116 | On-demand GSIs still have limits and hot keys (lsi-vs-gsi.md:36) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/gsi-throttling.html | Types of GSI throttling: GSI partition limits exceeded: Happens when individual GSI partitions exceed their throughput limits (hot partitions), even if overall GSI capacity appears sufficient. | 2026-11-08 | VERIFIED |
|
|
32
|
+
| DP-E117 | LSI queries auto-fetch unprojected attributes from base table (extra cost/latency); GSI cannot (lsi-vs-gsi.md:37; runtime-contract.md (Select)) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | Select (Request Parameters): If you query or scan a global secondary index, you can only request attributes that are projected into the index. Global secondary index queries cannot fetch attributes from the parent table. | 2026-11-08 | VERIFIED |
|
|
33
|
+
| DP-E118 | Up to 5 LSIs per table; default quota 20 GSIs per table (adjustable) (lsi-vs-gsi.md:38; workflow.md:202) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ServiceQuotas.html | Secondary indexes: You can define up to 5 local secondary indexes per table. There is a default quota of 20 global secondary indexes per table. | 2026-11-08 | VERIFIED |
|
|
34
|
+
| DP-E119 | LSI alternate sort values and GSI key combinations need not be unique (lsi-vs-gsi.md:39; modeling.md:100,70-72) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.html | Scenario: Using a Global Secondary Index: the key values in a global secondary index do not need to be unique. | 2026-11-08 | VERIFIED |
|
|
35
|
+
| DP-E120 | Indexes inherit the table's encryption key (LSI and GSI); key types AWS owned / AWS managed aws/dynamodb / customer managed (lsi-vs-gsi.md:40,111-112; workflow.md:203-205) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.howitworks.html | Customer managed keys: the DynamoDB table, local and global secondary indexes, and streams are encrypted with the same customer managed key. | 2026-11-08 | VERIFIED |
|
|
36
|
+
| DP-E121 | Query requires equality on one partition key (index PK for index queries) (lsi-vs-gsi.md:42-43,173-175) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | KeyConditionExpression: The condition must perform an equality test on a single partition key value. | 2026-11-08 | VERIFIED |
|
|
37
|
+
| DP-E122 | LSI item collection lives in one partition; cannot be split further (lsi-vs-gsi.md:44-45) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LSI.html | Item collections and partitions: In a table with one or more local secondary indexes, each item collection is stored in one partition. | 2026-11-08 | VERIFIED |
|
|
38
|
+
| DP-E123 | Vector indexes are read with SearchVectors and count toward the table's GSI quota (lsi-vs-gsi.md:47-50) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ServiceQuotas.html | Vector indexes: Vector indexes count toward the per-table quota for global secondary indexes, which has a default of 20. | 2026-11-08 | VERIFIED |
|
|
39
|
+
| DP-E124 | CFN LocalSecondaryIndexes property with IndexName, KeySchema (HASH/RANGE), Projection {ProjectionType: INCLUDE, NonKeyAttributes}; attribute must be in AttributeDefinitions (lsi-vs-gsi.md:69-81) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-dynamodb-table.html | Examples: DynamoDB Table with Local and Secondary Indexes: Projection: NonKeyAttributes: - Artist - NumberOfSongs ProjectionType: INCLUDE (inside LocalSecondaryIndexes: IndexName: myLSI, KeySchema with KeyType HASH and RANGE) | 2026-11-08 | VERIFIED |
|
|
40
|
+
| DP-E125 | LSI cannot be added to an existing table (CFN update of LocalSecondaryIndexes) (lsi-vs-gsi.md:33,164,214 vs CFN property docs) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-dynamodb-table.html | LocalSecondaryIndexes: CFN: "Update requires: No interruption" for LocalSecondaryIndexes; DynamoDB LSI.html: "Local secondary indexes on a table are created when the table is created." | 2026-11-08 | CONFLICT |
|
|
41
|
+
| DP-E126 | Non-transactional 1 KB write = 1 write unit; read unit baseline 4 KB; strong vs eventual differ; transactions cost more (modeling.md:121-123) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/read-write-operations.html | Capacity unit consumption for read/write operations: A strongly consistent read request of an item up to 4 KB requires one read unit. An eventually consistent read request of an item up to 4 KB requires one-half read unit. A transactional read request of an item up to 4 KB | 2026-11-08 | VERIFIED |
|
|
42
|
+
| DP-E127 | Query capacity: total size of all items returned rounded up to next 4 KB (not per item); filter/projection do not reduce consumed capacity (modeling.md:121-124; workflow.md; runtime-contract.md:43-44) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/read-write-operations.html | Capacity unit consumption for read operations: All items returned are treated as a single read operation, where DynamoDB computes the total size of all items. DynamoDB then rounds up the size to the next 4 KB boundary. | 2026-11-08 | VERIFIED |
|
|
43
|
+
| DP-E128 | TTL attribute: Number, epoch seconds (modeling.md:35-36) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html | Using time to live (TTL) in DynamoDB: The timestamp must be stored as a Number data type in Unix epoch time format at the seconds granularity. | 2026-11-08 | VERIFIED |
|
|
44
|
+
| DP-E129 | Query reads at most 1 MB or Limit evaluated items, then filters; Limit counts evaluated items; empty Items with LastEvaluatedKey possible (runtime-contract.md:40-42; workflow.md:229-230) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | Limit; Note on empty result set: A `Query` operation can return an empty result set and a `LastEvaluatedKey` if all the items read for the page of results are filtered out. | 2026-11-08 | VERIFIED |
|
|
45
|
+
| DP-E130 | End of results is signalled by empty/absent LastEvaluatedKey; non-empty does not mean more data (runtime-contract.md:40-42,17-22) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | LastEvaluatedKey (Response Elements): If `LastEvaluatedKey` is empty, then the "last page" of results has been processed and there is no more data to be retrieved. | 2026-11-08 | VERIFIED |
|
|
46
|
+
| DP-E131 | FilterExpression and ProjectionExpression do not reduce consumed capacity (runtime-contract.md:43-44; workflow.md:227-228) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | Intro note: The number of capacity units consumed will be the same whether you request all of the attributes (the default behavior) or just some of them (using a projection expression). The number will also be the same whether or no | 2026-11-08 | VERIFIED |
|
|
47
|
+
| DP-E132 | ExclusiveStartKey is a typed key map (value of prior LastEvaluatedKey) (runtime-contract.md:32-33) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | ExclusiveStartKey: The primary key of the first item that this operation will evaluate. Use the value that was returned for `LastEvaluatedKey` in the previous operation. | 2026-11-08 | VERIFIED |
|
|
48
|
+
| DP-E133 | AWS CLI --starting-token/NextToken are not interchangeable with service ExclusiveStartKey/LastEvaluatedKey (runtime-contract.md:33-34) | https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-pagination.html | How to use the --starting-token parameter: CLI page describes NextToken from CLI output passed to --starting-token; no sentence addresses (non-)interchangeability with ExclusiveStartKey. | 2026-11-08 | UNVERIFIED |
|
|
49
|
+
| DP-E134 | BatchGetItem: up to 100 items, 16 MB; partial results with UnprocessedKeys; no particular order (runtime-contract.md:47-49) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchGetItem.html | Intro: A single operation can retrieve up to 16 MB of data, which can contain as many as 100 items. `BatchGetItem` returns a partial result if the response size limit is exceeded, the table's provisioned throughput is exceeded, | 2026-11-08 | VERIFIED |
|
|
50
|
+
| DP-E135 | BatchGetItem results are unordered (runtime-contract.md:48-49) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchGetItem.html | Intro: DynamoDB does not return items in any particular order. | 2026-11-08 | VERIFIED |
|
|
51
|
+
| DP-E136 | BatchWriteItem: up to 25 puts/deletes, cannot update, no conditions, per-item atomic but batch not atomic, retry UnprocessedItems (runtime-contract.md:50-52) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchWriteItem.html | Intro: The individual `PutItem` and `DeleteItem` operations specified in `BatchWriteItem` are atomic; however `BatchWriteItem` as a whole is not. | 2026-11-08 | VERIFIED |
|
|
52
|
+
| DP-E137 | BatchWriteItem cannot carry conditions (runtime-contract.md:50) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchWriteItem.html | Intro: you cannot specify conditions on individual put and delete requests | 2026-11-08 | VERIFIED |
|
|
53
|
+
| DP-E138 | attribute_not_exists on the partition key prevents overwrite of an existing full primary key; ReturnValuesOnConditionCheckFailure ALL_OLD (runtime-contract.md:56-68; workflow.md:236) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutItem.html | Intro note; ReturnValuesOnConditionCheckFailure: To prevent a new item from replacing an existing item, use a conditional expression that contains the `attribute_not_exists` function with the name of the attribute being used as the partition key for the table. | 2026-11-08 | VERIFIED |
|
|
54
|
+
| DP-E139 | Conditional failures raise ConditionalCheckFailedException (runtime-contract.md:70-72) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateItem.html | Errors: ConditionalCheckFailedException: A condition specified in the operation failed to be evaluated. | 2026-11-08 | VERIFIED |
|
|
55
|
+
| DP-E140 | TransactWriteItems: up to 100 actions, 4 MB aggregate, same account and Region, no two actions on same item, ConditionCheck+Update same item not allowed (runtime-contract.md:73-76; workflow.md (txn)) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_TransactWriteItems.html | Intro: These actions can target items in different tables, but not in different AWS accounts or Regions, and no two actions can target the same item. For example, you cannot both `ConditionCheck` and `Update` the same item. The | 2026-11-08 | VERIFIED |
|
|
56
|
+
| DP-E141 | Transactions cannot be performed using indexes (runtime-contract.md:76) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis.html | TransactWriteItems API (Note): Transactions cannot be performed using indexes. | 2026-11-08 | VERIFIED |
|
|
57
|
+
| DP-E142 | ClientRequestToken deduplicates identical requests within a 10-minute window (runtime-contract.md:77-79) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_TransactWriteItems.html | ClientRequestToken: A client request token is valid for 10 minutes after the first request that uses it is completed. | 2026-11-08 | VERIFIED |
|
|
58
|
+
| DP-E143 | TTL cleanup eventual, usually within days; expired items can still be updated; use filter to hide (runtime-contract.md:90-92) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html | Using time to live (TTL) in DynamoDB: Items with valid, expired TTL attributes might be deleted by the system at any time, typically within a few days after their expiration. You can still update the expired items that are pending deletion | 2026-11-08 | VERIFIED |
|
|
59
|
+
| DP-E144 | MREC replicates asynchronously; strong read at a replica may be stale for writes from another Region (runtime-contract.md:94-96) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Multi-Region eventual consistency (MREC): Strongly consistent read operations return the latest version of an item if that item was last updated in the Region where the read occurred, but may return stale data if the item was last updated in a different Region. | 2026-11-08 | VERIFIED |
|
|
60
|
+
| DP-E145 | MREC transactions are not replicated atomically as a group (runtime-contract.md:95-96) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Transactions: Transactional writes are not replicated as a unit across Regions, meaning only some of the writes in a transaction might be returned by read operations in other replicas at a given point in time. | 2026-11-08 | VERIFIED |
|
|
61
|
+
| DP-E146 | MRSC requires three Regions (three replicas or two replicas plus a witness) (runtime-contract.md:98-99) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Multi-Region strong consistency (MRSC): A MRSC global table must be deployed in exactly three Regions. You can configure a MRSC global table with three replicas, or with two replicas and one witness. | 2026-11-08 | VERIFIED |
|
|
62
|
+
| DP-E147 | MRSC does not support TTL, LSIs or transaction APIs; GSIs supported but eventually consistent (runtime-contract.md:99,100) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | MRSC considerations; Transactions: Time to Live (TTL) is not supported for MRSC global tables. / Local secondary indexes (LSIs) are not supported for MRSC global tables. Global secondary indexes (GSIs) are supported. As with single-Region tables, reads fr | 2026-11-08 | VERIFIED |
|
|
63
|
+
| DP-E148 | PITR restore creates a new table (not in-place) (runtime-contract.md:103-104) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Point-in-time-recovery.html | Before you begin: When you restore the table, the backup restores to an independent table that is not part of the global table. | 2026-11-08 | VERIFIED |
|
|
64
|
+
| DP-E149 | A fixed (custom) TableName blocks CFN updates that require replacement; replacement needs a new name (runtime-contract.md:110-112; refactor.md:42-44,60-62) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-dynamodb-table.html | TableName: If you specify a name, you cannot perform updates that require replacement of this resource. You can perform updates that require no or some interruption. If you must replace the resource, specify a new name. | 2026-11-08 | VERIFIED |
|
|
65
|
+
| DP-E150 | Base-table key schema changes cannot be done in place via UpdateTable (need new table/migration) (runtime-contract.md:110; refactor.md:29) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateTable.html | Intro: UpdateTable "Modifies the provisioned throughput settings, global secondary indexes, DynamoDB Streams settings, or global table replica settings"; no sentence explicitly says key schema is immutable (CFN KeySchema page s | 2026-11-08 | UNVERIFIED |
|
|
66
|
+
| DP-E151 | Transaction API names do not map to IAM action names (authorized per item action incl. ConditionCheckItem) (workflow.md:206-209) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/specifying-conditions.html | Specifying conditions: Using condition keys (dynamodb:LeadingKeys): For `TransactGetItems` and `TransactWriteItems`, DynamoDB authorizes each item in the transaction separately. The authorization uses the action for that item (`dynamodb:GetItem`, `dynamodb:PutItem`, `dynamodb:UpdateItem` | 2026-11-08 | VERIFIED |
|
|
67
|
+
| DP-E152 | PartiQL API names do not map to IAM action names (workflow.md:208) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ql-iam.html | IAM security policies with PartiQL for DynamoDB: To read items using PartiQL for DynamoDB, you must have `dynamodb:PartiQLSelect` permission on the table or index. | 2026-11-08 | VERIFIED |
|
|
68
|
+
| DP-E153 | Vector index SearchSchema is separate from generic AttributeDefinitions; vector indexes use SearchSchema (design.md:35-38; workflow.md:62) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateTable.html | VectorIndexUpdates / Request Syntax: VectorIndexUpdates Create: "SearchSchema": [ { "AttributeName", "SearchSchemaElementType" } ] with VectorAttribute, Dimensions, DistanceFunction (request syntax shows SearchSchema as a distinct structure; the page has no | 2026-11-08 | UNVERIFIED |
|
|
69
|
+
| DP-E154 | GSI backfill indexes existing items that have the index key attributes, not application-derived keys that do not exist (refactor.md:28) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.OnlineOps.html | Phases of index creation (Backfilling): For each item in the table, DynamoDB determines which set of attributes to write to the index based on its projection (`KEYS_ONLY`, `INCLUDE`, or `ALL`). It then writes these attributes to the index. | 2026-11-08 | VERIFIED |
|
|
70
|
+
| DP-E155 | CFN completion does not mean the online-added GSI is ACTIVE (refactor.md:28,62-64) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-dynamodb-table.html | GlobalSecondaryIndexes: AWS CloudFormation doesn't wait for the index to complete creation because the backfilling phase can take a long time, depending on the size of the table. You can't use the index or update the table until the index's sta | 2026-11-08 | VERIFIED |
|
|
71
|
+
| DP-E156 | New LSI needs new-table migration, not an in-place UpdateTable edit (refactor.md:29) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LCICli.html | Create a table with a Local Secondary Index: Local Secondary Indexes must be created at the same time you create a table. | 2026-11-08 | VERIFIED |
|
|
72
|
+
| DP-E157 | UpdateItem creates the item if missing; use attribute_exists to make update-only (refactor.md:32-33) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateItem.html | Intro; ConditionExpression: Edits an existing item's attributes, or adds a new item to the table if it does not already exist. (ConditionExpression allows function `attribute_exists`.) | 2026-11-08 | VERIFIED |
|
|
73
|
+
| DP-E158 | Key attributes cannot be changed by an UpdateExpression; moving a primary-key value needs a new item (refactor.md:32-34) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.UpdateExpressions.html | Using update expressions in DynamoDB: Searched UpdateItem API page and Update Expressions page: no sentence stating key attributes cannot be updated. | 2026-11-08 | UNVERIFIED |
|
|
74
|
+
| DP-E159 | Custom-named table replacement requires a distinct name (refactor.md:42-44) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-dynamodb-table.html | TableName: If you must replace the resource, specify a new name. | 2026-11-08 | VERIFIED |
|
|
75
|
+
| DP-E160 | CFN "Update requires" label for KeySchema/LSI is not proof that in-place edit is allowed (refactor.md:42-43 (CFN interruption label)) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-dynamodb-table.html | KeySchema; LocalSecondaryIndexes: KeySchema: "Update requires: Some interruptions"; LocalSecondaryIndexes: "Update requires: No interruption" (while LSI.html says LSIs are created only with the table). | 2026-11-08 | VERIFIED |
|
|
76
|
+
| DP-E201 | AttributeValue tags S,N,B,BOOL,NULL,L,M,SS,NS,BS; sets homogeneous, unique, unordered, no empty sets (D:12-21, typed-vector-item.json) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html | Sets: "Each value within a set must be unique. The order of the values within a set is not preserved... DynamoDB does not support empty sets" | 2026-11-08 | VERIFIED |
|
|
77
|
+
| DP-E202 | Empty lists/maps allowed (differ from empty sets) (D:23-24) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html | Data types / Document types: "An attribute value cannot be an empty set (string set, number set, or binary set), however, empty lists and maps are allowed." | 2026-11-08 | VERIFIED |
|
|
78
|
+
| DP-E203 | List is ordered, may mix types (D:19, D:23) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html | List: "A list type attribute can store an ordered collection of values." / "the elements in a list element do not have to be of the same type." | 2026-11-08 | VERIFIED |
|
|
79
|
+
| DP-E204 | Key scalar types are S/N/B (not L/M/sets) (D:23) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html | Scalar types / primary key: "The scalar types are number, string, binary, Boolean, and null." (key-type restriction S/N/B is on the page's primary-key section; fetched text only confirmed the scalar list) | 2026-11-08 | UNVERIFIED |
|
|
80
|
+
| DP-E205 | Embedding stored as L of N elements (not NS, no VECTOR tag) (D:35-37, 5) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | Generating vector embeddings: "Store that vector in a DynamoDB item, in the attribute named by the vector index ( VectorAttribute ), as a list ( L ) of numbers ( N )." | 2026-11-08 | VERIFIED |
|
|
81
|
+
| DP-E206 | DynamoDB does not generate embeddings (D:37, E:104) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | Generating vector embeddings: "DynamoDB stores and searches vector embeddings, but it does not generate them." | 2026-11-08 | VERIFIED |
|
|
82
|
+
| DP-E207 | Same model and dimensions for stored and query vectors (D:37-38) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | Query vector and stored vectors must use the same model: "must be produced by the same embedding model and must have the same number of dimensions as the vector index." | 2026-11-08 | VERIFIED |
|
|
83
|
+
| DP-E208 | Vector index uses float32; extra precision lost in index (D:38-39, E:39) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearch.Requirements.html | Requirements and limitations: "Vector embeddings are stored in the index at 32-bit floating point (f32) precision. Higher-precision values are accepted but lose precision when replicated to the index." | 2026-11-08 | VERIFIED |
|
|
84
|
+
| DP-E209 | Approximate nearest-neighbor search (D:49) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearch.html | Using vector indexes in DynamoDB: "vector indexes use approximate nearest neighbor (ANN) search to find items whose vectors are most similar" | 2026-11-08 | VERIFIED |
|
|
85
|
+
| DP-E210 | Eventually consistent search; not strong even with MRSC base table (D:49-50, C:326) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearch.html | Using vector indexes with other DynamoDB features (Global tables): "The MRSC guarantee covers the table, not the vector index... a delay occurs between the time a write is acknowledged and the time that vector becomes searchable" | 2026-11-08 | VERIFIED |
|
|
86
|
+
| DP-E211 | Native vector search does not require OpenSearch / separate vector DB (D:49-51) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearch.html | intro: "perform similarity searches without needing a separate vector database." | 2026-11-08 | VERIFIED |
|
|
87
|
+
| DP-E212 | Vector indexes not accessible via Query/Scan/PartiQL (D:51, 116-119) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearch.Requirements.html | Requirements and limitations: "Vector indexes do not support Query or Scan operations." / "Vector indexes are not accessible through PartiQL." | 2026-11-08 | VERIFIED |
|
|
88
|
+
| DP-E213 | SearchVectors has no pagination; 16 MB response limit (D:52, 130-131) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearch.Requirements.html | Requirements and limitations: "SearchVectors responses are limited to 16 MB. Pagination is not supported." | 2026-11-08 | VERIFIED |
|
|
89
|
+
| DP-E214 | Vector indexes require on-demand (PAY_PER_REQUEST) (D:118-119, vector-create-table.json BillingMode) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearch.Requirements.html | Requirements and limitations: "Vector indexes use on-demand capacity mode only, and they require a table that also uses on-demand capacity mode." | 2026-11-08 | VERIFIED |
|
|
90
|
+
| DP-E215 | Dimensions 1-4,096 (D:120, vector-table.cfn.yaml Dimensions) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-dynamodb-table-vectorindex.html | Properties: Dimensions: "Type : Integer Minimum : 1 Maximum : 4096 Update requires : Updates are not supported." | 2026-11-08 | VERIFIED |
|
|
91
|
+
| DP-E216 | TopK 1-100 (D:120) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_SearchVectors.html | TopK: "The number of most similar results to return. Valid values range from 1 to 100, inclusive." | 2026-11-08 | VERIFIED |
|
|
92
|
+
| DP-E217 | One optional HASH; up to 18 inline filters (D:122, E:110) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ServiceQuotas.html | Vector indexes: "Maximum partition keys ( HASH ) per vector index 1 No ... Number of inline filters per vector index 18 No" | 2026-11-08 | VERIFIED |
|
|
93
|
+
| DP-E218 | If HASH configured, every search must supply its value (D:122-123) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearch.html | SearchSchema: "If you define a vector index partition key in the SearchSchema, you must provide its value in the SearchConditionExpression when you call SearchVectors." | 2026-11-08 | VERIFIED |
|
|
94
|
+
| DP-E219 | Missing HASH attribute: write succeeds but item not indexed; wrong dimension rejected; missing inline filter still indexed (D:123-124) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | Writing items with vector data: "Vector index partition key attribute is missing: Write succeeds on the base table, but the item is not replicated to the vector index." | 2026-11-08 | VERIFIED |
|
|
95
|
+
| DP-E220 | Index config (dimensions, distance, projection, schema) immutable (D:125-126) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-dynamodb-table-vectorindex.html | Properties (all): "Update requires : Updates are not supported." (on Dimensions, DistanceFunction, Projection, SearchSchema, VectorAttribute); also VectorSearch.html: "You cannot change the set of included attributes after the vector inde | 2026-11-08 | VERIFIED |
|
|
96
|
+
| DP-E221 | Default 5 vector indexes, up to 20; count toward GSI quota (D:127-129) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ServiceQuotas.html | Vector indexes: "Vector indexes count toward the per-table quota for global secondary indexes, which has a default of 20." | 2026-11-08 | VERIFIED |
|
|
97
|
+
| DP-E222 | Only one vector/GSI index create or delete at a time per table (D:128) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | Adding a vector index to an existing table: "You can create or delete only one vector index per table at a time. This limit is shared with global secondary index creation on the same table." | 2026-11-08 | VERIFIED |
|
|
98
|
+
| DP-E223 | Every SearchSchema attribute (HASH and INLINE_FILTER) must be in AttributeDefinitions; Embedding is not (D:63-67, vector-create-table.json AttributeDefinitions) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-dynamodb-table-vectorindex.html | Properties: SearchSchema: "Every attribute that you reference in SearchSchema must also be declared in the table's AttributeDefinitions" (Embedding-not-declared inferred from CLI example, which declares only ProductId/Category/Brand) | 2026-11-08 | VERIFIED |
|
|
99
|
+
| DP-E224 | SearchVector is a bare array of Number AttributeValues, not L wrapper (D:102-103, vector-search.json SearchVector) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | Searching with SearchVectors: "The SearchVector request parameter is a plain JSON array of number objects ... Do not wrap it in a DynamoDB L type" | 2026-11-08 | VERIFIED |
|
|
100
|
+
| DP-E225 | SearchConditionExpression (not FilterExpression); only equality on declared top-level search-schema attrs (D:104-106, 63) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_SearchVectors.html | SearchConditionExpression: "The HASH and INLINE_FILTER attributes support only the equality operator ( = ). You can reference only top-level attributes from the search schema." | 2026-11-08 | VERIFIED |
|
|
101
|
+
| DP-E226 | Response SearchResults has Item and Score; lower better for COSINE/EUCLIDEAN, higher for DOT_PRODUCT (D:106-107) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | Basic search: "For COSINE and EUCLIDEAN , lower scores indicate greater similarity. For DOT_PRODUCT , higher scores indicate greater similarity." | 2026-11-08 | VERIFIED |
|
|
102
|
+
| DP-E227 | Embedding not returned by default; request explicitly (D:108) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | Vector attributes are excluded from results by default: "By default, the results from SearchVectors don't include the vector attribute (the embedding)... To include the vector attribute, request it with a ProjectionExpression." | 2026-11-08 | VERIFIED |
|
|
103
|
+
| DP-E228 | Index ACTIVE then search endpoint may lag; ValidationException transient (D:110-113) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | A newly ready index is not immediately searchable: "After DescribeTable first reports IndexStatus ACTIVE , the search endpoint can require additional time... SearchVectors returns a ValidationException" | 2026-11-08 | VERIFIED |
|
|
104
|
+
| DP-E229 | SearchVectors request names: TableName, IndexName, SearchVector, TopK, SearchConditionExpression, ExpressionAttributeNames/Values, ReturnConsumedCapacity (INDEXES/TOTAL/NONE), ProjectionExpression (D:108, vector-search.json ReturnConsumedCapacity "INDEXES"; CLI flags) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_SearchVectors.html | Request Syntax / Request Parameters: "Valid Values: INDEXES / TOTAL / NONE" | 2026-11-08 | VERIFIED |
|
|
105
|
+
| DP-E230 | VectorIndexes members IndexName, VectorAttribute{AttributeName}, Dimensions, DistanceFunction (COSINE/EUCLIDEAN/DOT_PRODUCT), SearchSchema[{AttributeName,SearchSchemaElementType HASH/INLINE_FILTER}], Projection{ProjectionType,NonKeyAttributes}; INCLUDE valid (assets/vector-create-table.json; vector-table.cfn.yaml; D:81-85) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-dynamodb-table-searchschemaelement.html | Properties: "Allowed values : HASH / INLINE_FILTER" (also vectorindex page: "Allowed values : COSINE / DOT_PRODUCT / EUCLIDEAN"; Projection page lists NonKeyAttributes, ProjectionType) | 2026-11-08 | VERIFIED |
|
|
106
|
+
| DP-E231 | describe-table exposes VectorIndexes (D:84-85) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/create-table.html | Output (VectorIndexes): "VectorIndexes -> (list) The vector indexes, if any, on the table." (create-table page output; same TableDescription shape as describe-table, describe-table page not separately fetched) | 2026-11-08 | VERIFIED |
|
|
107
|
+
| DP-E232 | IAM action dynamodb:SearchVectors on vector index ARN table/T/index/I (D:139-141, vector-search-policy) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/iam-policy-example-search-vectors.html | IAM policy to grant access to search a vector index: "arn:aws:dynamodb:us-west-2:123456789012:table/Products/index/ProductEmbeddingIndex" with "Action": "dynamodb:SearchVectors" | 2026-11-08 | VERIFIED |
|
|
108
|
+
| DP-E233 | Creating/deleting vector indexes needs only existing CreateTable/UpdateTable permissions (D:141-142) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/iam-policy-example-search-vectors.html | No additional permissions required: "No additional IAM permissions are required to create or delete vector indexes. The existing dynamodb:CreateTable and dynamodb:UpdateTable permissions are sufficient." | 2026-11-08 | VERIFIED |
|
|
109
|
+
| DP-E234 | FGAC keys LeadingKeys, Attributes, Select unsupported for SearchVectors (D:145) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/iam-policy-example-search-vectors.html | FGAC condition keys not supported for SearchVectors: "You cannot use dynamodb:LeadingKeys , dynamodb:Attributes , or dynamodb:Select condition keys to restrict SearchVectors access." | 2026-11-08 | VERIFIED |
|
|
110
|
+
| DP-E235 | HASH tenant routing is not IAM tenant isolation (D:146-151, E:204-206) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchWorkingWith.html | Partition key scoping is not a security boundary: "Any principal that holds dynamodb:SearchVectors permission on the index can search any partition key value." | 2026-11-08 | VERIFIED |
|
|
111
|
+
| DP-E236 | Number: up to 38 digits; positive range 1E-130 to ~1e126 plus negative and zero (E:38, 59-60) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html | Number: "Numbers can have up to 38 digits of precision... Positive range: 1E-130 to 9.9999999999999999999999999999999999999E+125" | 2026-11-08 | VERIFIED |
|
|
112
|
+
| DP-E237 | 400 KB item limit (E:215) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html | Document types / Sets: "as long as the item containing the values fits within the DynamoDB item size limit (400 KB)." | 2026-11-08 | VERIFIED |
|
|
113
|
+
| DP-E238 | Titan V2 model id amazon.titan-embed-text-v2:0; params inputText, dimensions (1024 default, 512, 256), normalize, embeddingTypes ["float"]; response key embedding (E:104-106, C:267, bedrock-embedding-input.json) | https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-titan-embed-text.html | Request and response (V2): "dimensions – (optional)... The following values are accepted: 1024 (default), 512, 256." and "embedding – An array that represents the embedding vector of the input you provided. This will always be type float ." | 2026-11-08 | VERIFIED |
|
|
114
|
+
| DP-E239 | embeddingTypes accepts "float"/"binary"; normalize optional (E:104-105, assets) | https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-titan-embed-text.html | V2 Request: "embeddingTypes – (optional) Accepts a list containing "float", "binary", or both. Defaults to float ." / "normalize ... Defaults to true." | 2026-11-08 | VERIFIED |
|
|
115
|
+
| DP-E240 | model id string literal (E:104) | https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-titan-embed-text.html | Example code: `model_id = "amazon.titan-embed-text-v2:0"` | 2026-11-08 | VERIFIED |
|
|
116
|
+
| DP-E241 | S3 Vectors data.float32; higher precision converted to float32 (E:40, 159) | https://docs.aws.amazon.com/AmazonS3/latest/API/API_S3VectorBuckets_PutVectors.html | Description (note): "If you pass higher-precision values to an AWS SDK, S3 Vectors converts the values to 32-bit floating point before storing them" | 2026-11-08 | VERIFIED |
|
|
117
|
+
| DP-E242 | PutVectors uses vectors[].{key,data.float32,metadata}; QueryVectors uses queryVector.float32, topK, returnMetadata (E:159-160, 164-184, C:363) | https://docs.aws.amazon.com/AmazonS3/latest/API/API_S3VectorBuckets_VectorData.html | Contents: "float32 - The vector data as 32-bit floating point numbers." (PutInputVector page: data, key, metadata; QueryVectors page: queryVector, topK, returnMetadata) | 2026-11-08 | VERIFIED |
|
|
118
|
+
| DP-E243 | Vector key identifies vector within its index (E:186) | https://docs.aws.amazon.com/AmazonS3/latest/API/API_S3VectorBuckets_PutInputVector.html | key: "The name of the vector. The key uniquely identifies the vector in a vector index." | 2026-11-08 | VERIFIED |
|
|
119
|
+
| DP-E244 | S3 Vectors writes strongly consistent (E:188) | https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-vectors.html | What is Amazon S3 Vectors?: "Writes to S3 Vectors are strongly consistent, which means that you can immediately" (search-result excerpt, page text truncated at that point) | 2026-11-08 | VERIFIED |
|
|
120
|
+
| DP-E245 | KB StorageConfiguration lists S3_VECTORS, not DynamoDB (E:154-157) | https://docs.aws.amazon.com/bedrock/latest/APIReference/API_agent_StorageConfiguration.html | type: "Valid Values: OPENSEARCH_SERVERLESS / PINECONE / REDIS_ENTERPRISE_CLOUD / RDS / MONGO_DB_ATLAS / NEPTUNE_ANALYTICS / OPENSEARCH_MANAGED_CLUSTER / S3_VECTORS" | 2026-11-08 | VERIFIED |
|
|
121
|
+
| DP-E246 | KB with S3 Vectors fetches from S3 source, chunks, embeds, stores in vector index (E:145-152) | https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-vectors-bedrock-kb.html | Integration overview: "When creating a knowledge base in Amazon Bedrock, you can select S3 Vectors as your vector store." | 2026-11-08 | VERIFIED |
|
|
122
|
+
| DP-E248 | Neither service exposes a float64 vector selection (E:61-64) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearch.Requirements.html | Requirements / Contents: Only f32 documented: "Vector embeddings are stored in the index at 32-bit floating point (f32) precision." and VectorData union has only float32 | 2026-11-08 | VERIFIED |
|
|
123
|
+
| DP-E249 | bedrock-runtime invoke-model flags --model-id, --body, --content-type, --accept, positional outfile; --cli-binary-format raw-in-base64-out (C:273-277) | https://docs.aws.amazon.com/cli/latest/reference/bedrock-runtime/invoke-model.html | Synopsis / Options: "--body (blob)", "--content-type (string)", "--accept (string)", "--model-id (string) [required]", "outfile (string) [required]"; "The raw-in-base64-out format preserves compatibility with AWS CLI V1 behavior" | 2026-11-08 | VERIFIED |
|
|
124
|
+
| DP-E250 | dynamodb search-vectors flags --table-name, --index-name, --search-vector, --top-k, --search-condition-expression, --expression-attribute-names/values; no pagination in operation (C:315-320, D:98) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/search-vectors.html | Options: "--search-vector (list) [required]"; "--top-k (integer) [required]"; "--search-condition-expression (string)" | 2026-11-08 | VERIFIED |
|
|
125
|
+
| DP-E251 | s3vectors put-vectors --index-arn, --vectors; query-vectors --index-arn, --query-vector, --top-k, --return-distance, --return-metadata, --no-paginate (C:356-360) | https://docs.aws.amazon.com/cli/latest/reference/s3vectors/query-vectors.html | Options: "--top-k (integer) [required]"; "--query-vector (tagged union structure) [required]"; "--return-metadata / --no-return-metadata"; "--return-distance / --no-return-distance"; "query-vectors is a paginated operation." | 2026-11-08 | VERIFIED |
|
|
126
|
+
| DP-E252 | Query with metadata or filter needs s3vectors:GetVectors besides QueryVectors; writes need PutVectors (C:364-366) | https://docs.aws.amazon.com/AmazonS3/latest/API/API_S3VectorBuckets_QueryVectors.html | Permissions: "If you specify a metadata filter or set returnMetadata to true, you must have both s3vectors:QueryVectors and s3vectors:GetVectors permissions." (PutVectors page: "You must have the s3vectors:PutVectors permission") | 2026-11-08 | VERIFIED |
|
|
127
|
+
| DP-E253 | PutVectors can overwrite an existing key (C:330-333) | https://docs.aws.amazon.com/AmazonS3/latest/API/API_S3VectorBuckets_PutVectors.html | Description: Page fetched; no sentence about overwrite found in extracted text (key "uniquely identifies the vector in a vector index" only) | 2026-11-08 | UNVERIFIED |
|
|
128
|
+
| DP-E254 | bedrock-agent start-ingestion-job --knowledge-base-id --data-source-id --client-token; token 33-256 chars; response ingestionJob.ingestionJobId (C:386-388, 384-385) | https://docs.aws.amazon.com/cli/latest/reference/bedrock-agent/start-ingestion-job.html | Options: "--client-token (string) ... min: 33 max: 256" | 2026-11-08 | VERIFIED |
|
|
129
|
+
| DP-E255 | get-ingestion-job flags; ingestionJob.status COMPLETE; statistics, failureReasons (C:397-413) | https://docs.aws.amazon.com/cli/latest/reference/bedrock-agent/get-ingestion-job.html | Options / Output: "--ingestion-job-id (string) [required]"; output "ingestionJob -> (structure)", "statistics -> (structure)", "failureReasons -> (list)", status value "COMPLETE" | 2026-11-08 | VERIFIED |
|
|
130
|
+
| DP-E256 | bedrock-agent-runtime retrieve --knowledge-base-id, --retrieval-query, --retrieval-configuration vectorSearchConfiguration.numberOfResults; paginated with nextToken (C:416-419, 422-426) | https://docs.aws.amazon.com/cli/latest/reference/bedrock-agent-runtime/retrieve.html | Options / Output: "retrieve is a paginated operation... You can disable pagination by providing the --no-paginate argument." and "the response returns a nextToken" | 2026-11-08 | VERIFIED |
|
|
131
|
+
| DP-E301 | Table ARN `arn:<partition>:dynamodb:<region>:<owner>:table/<table>`; GSI and LSI both `<table-arn>/index/<name>`; stream `<table-arn>/stream/<label>` (iam-and-access.md:18-20) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Resource types defined by Amazon DynamoDB: arn:${Partition}:dynamodb:${Region}:${Account}:table/${TableName}/index/${IndexName} ; .../table/${TableName}/stream/${StreamLabel} | 2026-11-08 | VERIFIED |
|
|
132
|
+
| DP-E302 | GetItem/PutItem/UpdateItem/DeleteItem scope = table; Query/Scan = table plus index ARNs (iam-and-access.md:29-31) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Actions defined by Amazon DynamoDB: Query: "Grants permission to use the primary key of a table or a secondary index to directly access items from that table or index" (resource types table*, index); GetItem resource: table* | 2026-11-08 | VERIFIED |
|
|
133
|
+
| DP-E303 | SearchVectors is an IAM action on a vector index ARN (`.../table/T/index/I`) (iam-and-access.md:32; assets/vector-search-policy.json:7-8) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Actions defined by Amazon DynamoDB: SearchVectors: "Grants permission to perform a vector similarity search on a vector index associated with an Amazon DynamoDB table" (resource type index*) | 2026-11-08 | VERIFIED |
|
|
134
|
+
| DP-E304 | TransactGetItems uses GetItem; TransactWriteItems uses Put/Update/Delete and ConditionCheckItem; no `dynamodb:TransactWriteItems`/`TransactGetItems` IAM action; ConditionCheckItem is permission-only; `dynamodb:EnclosingOperation` condition key (iam-and-access.md:33-34,45-49) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis-iam.html | Using IAM with DynamoDB transactions: "Permissions for Put, Update, Delete, and Get actions are governed by the permissions used for the underlying PutItem, UpdateItem, DeleteItem, and GetItem operations. For the ConditionCheck action, you can use the dynamo | 2026-11-08 | VERIFIED |
|
|
135
|
+
| DP-E305 | Transactions: same-account / same-Region boundary (iam-and-access.md:34) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis.html | TransactWriteItems API: "These actions can target up to 100 distinct items in one or more DynamoDB tables within the same AWS account and in the same Region." | 2026-11-08 | VERIFIED |
|
|
136
|
+
| DP-E306 | PartiQL IAM actions PartiQLSelect/Insert/Update/Delete; select on table/index, writes on table; `dynamodb:ExecuteStatement` is not an IAM action (iam-and-access.md:35,46) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Actions defined by Amazon DynamoDB: PartiQLSelect: "Grants permission to read a set of attributes for items from a table or index" (index); PartiQLInsert/Update/Delete resource table*; ExecuteStatement API maps to dynamodb:PartiQL* actions | 2026-11-08 | VERIFIED |
|
|
137
|
+
| DP-E307 | Describe/Create/Update/DeleteTable, Describe/UpdateTimeToLive, Describe/UpdateContinuousBackups actions on table (iam-and-access.md:36-38) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Actions defined by Amazon DynamoDB: UpdateContinuousBackups: "Grants permission to enable or disable continuous backups" (table*); UpdateTimeToLive: "Grants permission to enable or disable TTL for the specified table" (table*) | 2026-11-08 | VERIFIED |
|
|
138
|
+
| DP-E308 | DescribeStream/GetShardIterator/GetRecords use `dynamodb:` prefix, resource = stream ARN (iam-and-access.md:39; assets/stream-read-policy.json:7-8) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Actions defined by Amazon DynamoDB: GetRecords: "Grants permission to retrieve the stream records from a given shard" (stream*, access level Read); action column dynamodb:GetRecords | 2026-11-08 | VERIFIED |
|
|
139
|
+
| DP-E309 | ListTables/ListStreams/DescribeLimits/DescribeEndpoints have no resource-level support (`Resource: "*"`) (iam-and-access.md:40) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Actions defined by Amazon DynamoDB: ListTables: "Grants permission to return an array of table names associated with the current account and endpoint" (no resource type listed); same for the other three | 2026-11-08 | VERIFIED |
|
|
140
|
+
| DP-E310 | TagResource/UntagResource/ListTagsOfResource apply to table or stream (iam-and-access.md:41) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Actions defined by Amazon DynamoDB: TagResource: "Grants permission to associate a set of tags with an Amazon DynamoDB resource" - resource types stream* and table* | 2026-11-08 | VERIFIED |
|
|
141
|
+
| DP-E311 | Get/Put/DeleteResourcePolicy apply to table or stream; policy on stream allowed; index has no independent policy (iam-and-access.md:42,120-124) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutResourcePolicy.html | Request Parameters (ResourceArn): "The resources you can specify include tables and streams. You can control index permissions using the base table's policy." | 2026-11-08 | VERIFIED |
|
|
142
|
+
| DP-E312 | GetAbacStatus/UpdateAbacStatus are IAM actions, `Resource: "*"`, account/Region setting (iam-and-access.md:43,114-117) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/abac-enable-streams.html | IAM permissions required to enable Streams ABAC: "You need the dynamodb:UpdateAbacStatus permission to enable Streams ABAC for your account in the current Region." (example policy uses "Resource": "*") | 2026-11-08 | VERIFIED |
|
|
143
|
+
| DP-E313 | CLI (inspected 2.37.4) has no `dynamodb get-abac-status`; IAM action name is not evidence a CLI op exists (iam-and-access.md:114-117). Note: absence consistent with claim; version-specific | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/index.html | Available Commands (AWS CLI 2.39.6): No sentence; the 2.39.6 dynamodb command index contains no abac command (searched for "abac": 0 hits). Absence only. | 2026-11-08 | UNVERIFIED |
|
|
144
|
+
| DP-E314 | table-index-read-policy grants GetItem/BatchGetItem on table and Query on table + GSI1; `/index/*` pattern covers indexes (iam-and-access.md:51-53) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/iam-policy-specific-table-indexes.html | IAM policy to grant access to a specific DynamoDB table and its indexes: "arn:aws:dynamodb:us-west-2:123456789012:table/Books", "arn:aws:dynamodb:us-west-2:123456789012:table/Books/index/*" | 2026-11-08 | VERIFIED |
|
|
145
|
+
| DP-E315 | `dynamodb:LeadingKeys` supported on some actions; Scan does not support LeadingKeys (iam-and-access.md:59-60) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Actions defined by Amazon DynamoDB: Scan row condition keys: aws:ResourceTag, dynamodb:Attributes, ReturnConsumedCapacity, ReturnValues, Select (no dynamodb:LeadingKeys); Query row lists dynamodb:LeadingKeys. Also https://docs.aws.amazon.com/amazondynamodb | 2026-11-08 | VERIFIED |
|
|
146
|
+
| DP-E316 | CLI `accessanalyzer validate-policy --policy-type IDENTITY_POLICY --policy-document`; `iam simulate-custom-policy --policy-input-list --action-names --resource-arns` (iam-and-access.md:63-73) | https://docs.aws.amazon.com/cli/latest/reference/iam/simulate-custom-policy.html | Options: Page lists `--policy-input-list` and `--resource-arns` options (confirmed by text search); validate-policy page lists `--policy-type` (accessanalyzer/validate-policy.html) | 2026-11-08 | VERIFIED |
|
|
147
|
+
| DP-E317 | Table tags inherited by indexes; indexes cannot be tagged directly (iam-and-access.md:83). Note: inheritance); "cannot be tagged directly" is consistent with SAR (tag actions list only table*/stream* | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/attribute-based-access-control.html | Using attribute-based access control with DynamoDB: "The indexes associated with a table inherit the tags you add to the table." | 2026-11-08 | VERIFIED |
|
|
148
|
+
| DP-E318 | Streams: independent tags/ABAC, no inheritance of table tags, not taggable at creation (iam-and-access.md:83-85,96-99,102) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.Streams.html | Tagging DynamoDB Streams: "DynamoDB Streams does not currently support tagging on creation. You can only add tags to existing streams." ; abac-streams.html: "Stream resources do not inherit tags from their parent table" | 2026-11-08 | VERIFIED |
|
|
149
|
+
| DP-E319 | CLI `dynamodb tag-resource --resource-arn --tags Key=,Value=`, `list-tags-of-resource`, `untag-resource --tag-keys` (iam-and-access.md:88-99) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.Streams.html | Tagging existing streams (AWS CLI): "aws dynamodb tag-resource --resource-arn arn:aws:dynamodb:us-east-1:111122223333:table/Movies/stream/2024-01-01T00:00:00.000 --tags Key=Owner,Value=blueTeam" ; untag-resource --tag-keys per CLI reference | 2026-11-08 | VERIFIED |
|
|
150
|
+
| DP-E320 | Tag on create uses CreateTable `--tags`; CreateTable with tags needs TagResource permission (iam-and-access.md:102-103). Note: flag exists; permission requirement not located | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/create-table.html | Synopsis: Synopsis contains `[--tags <value>]`. The extra-TagResource-permission claim: no sentence found on any fetched page (SAR CreateTable row lists aws:RequestTag/aws:TagKeys only, no dependent action listed beyond AssociateT | 2026-11-08 | UNVERIFIED |
|
|
151
|
+
| DP-E321 | ABAC enablement independent for tables and Streams, account/Region scoped; audit first; opt-out window (iam-and-access.md:106-109) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/abac-enable-streams.html | Enabling ABAC for DynamoDB Streams: "After you enable Streams ABAC, you can opt out within the next seven calendar days of opting in." ; abac-streams.html: "Enabling ABAC for tables does not automatically enable it for streams in your account." | 2026-11-08 | VERIFIED |
|
|
152
|
+
| DP-E322 | `aws:ResourceTag`, `aws:RequestTag`, `aws:TagKeys` support varies by action/resource (iam-and-access.md:110-111). Note: SAR page is JavaScript-rendered; condition keys not readable in this pass | https://docs.aws.amazon.com/service-authorization/latest/reference/list_dynamodb.html | Actions defined by Amazon DynamoDB: e.g. TagResource lists aws:RequestTag/aws:ResourceTag/aws:TagKeys; UntagResource lists ResourceTag + TagKeys only; DescribeLimits lists none | 2026-11-08 | UNVERIFIED |
|
|
153
|
+
| DP-E323 | When ABAC disabled, tag conditions evaluate differently (as if no tags) (iam-and-access.md:111-112) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/abac-streams.html | Condition keys to implement ABAC with DynamoDB Streams: "When DynamoDB Streams ABAC is not enabled for your account, aws:ResourceTag conditions are evaluated as if no tags are attached to the stream resource." | 2026-11-08 | VERIFIED |
|
|
154
|
+
| DP-E324 | Cross-account needs resource policy AND caller identity policy; use full table ARN, a bare name resolves in caller account (iam-and-access.md:126-132) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/rbac-cross-account-access.html | Cross-account access with resource-based policies in DynamoDB: "If you only provide the table name parameter instead of a complete ARN, the API operation will be performed on the table in the account to which the requestor belongs." | 2026-11-08 | VERIFIED |
|
|
155
|
+
| DP-E325 | Resource-policy support does not imply cross-account for every API (policy admin, TTL/PITR, PartiQL differ) (iam-and-access.md:128-131) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/rbac-iam-actions.html | Resource-based policy API operations / TTL / PartiQL: "GetResourcePolicy Yes No ... UpdateTimeToLive Yes No ... ExecuteStatement Yes No" (resource-based policy support / cross-account support); Continuous backups rows Yes/No | 2026-11-08 | VERIFIED |
|
|
156
|
+
| DP-E326 | AWS-managed-key table encryption does not support cross-account resource-policy path; CMK needs cross-account KMS authorization (iam-and-access.md:131-132; encryption.md:(file line 176-?) see E352). Note: AWS-managed part); CMK authorization part UNVERIFIED | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/rbac-considerations.html | Cross-account considerations: "Cross-account access using resource-based policies doesn't support encrypted tables with AWS managed keys because you can't grant cross-account access to the AWS managed KMS policy." (CMK cross-account KMS part: not sta | 2026-11-08 | VERIFIED |
|
|
157
|
+
| DP-E327 | `dynamodb get-resource-policy --resource-arn`; `put-resource-policy --policy --expected-revision-id` (iam-and-access.md:134-143) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/put-resource-policy.html | Options: "--expected-revision-id (string) A string value that you can use to conditionally update your policy." | 2026-11-08 | VERIFIED |
|
|
158
|
+
| DP-E328 | `NO_POLICY` for conditional attach; revision mismatch or absence both give PolicyNotFoundException (iam-and-access.md:145-147) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutResourcePolicy.html | Request Parameters (ExpectedRevisionId): "if the revision ID of the existing policy on the resource doesn't match or if there's no policy attached to the resource, your request will be rejected with a PolicyNotFoundException. To conditionally attach a policy wh | 2026-11-08 | VERIFIED |
|
|
159
|
+
| DP-E329 | Successful policy writes have an update-interval restriction; propagation is bounded/eventually consistent (iam-and-access.md:148-149) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/rbac-considerations.html | General considerations: "Subsequent updates to a policy for a given resource are blocked for 15 seconds after a successful update of the policy for the same resource." | 2026-11-08 | VERIFIED |
|
|
160
|
+
| DP-E330 | `--confirm-remove-self-resource-access` flag exists (iam-and-access.md:149-150) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/put-resource-policy.html | Options: "--confirm-remove-self-resource-access / --no-confirm-remove-self-resource-access (boolean) Set this parameter to true to confirm that you want to remove your permissions to change the policy of this resource in the futu | 2026-11-08 | VERIFIED |
|
|
161
|
+
| DP-E331 | Explicit deny of the global-table SLR replication action breaks adding/deleting replicas (iam-and-access.md:150-152) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/rbac-considerations.html | Global table considerations: "if the action for a DynamoDB service-linked role (SLR) to replicate data for a global table is denied, adding or deleting a replica will fail with an error." | 2026-11-08 | VERIFIED |
|
|
162
|
+
| DP-E332 | CloudFormation-managed policy content: no drift repair after out-of-band edit (iam-and-access.md:152-153) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/rbac-considerations.html | CloudFormation considerations: "Resource-based policies don't support drift detection. If you update a resource-based policy outside of the AWS CloudFormation stack template, you'll need to update the CloudFormation stack" | 2026-11-08 | VERIFIED |
|
|
163
|
+
| DP-E333 | Resource policy document shape (Principal, Action dynamodb:GetItem/Query, table + index ARNs) (assets/table-resource-policy.json:1-22) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutResourcePolicy.html | Examples: `"Principal": {"AWS":[...]},"Action":["dynamodb:GetItem"],"Resource":"arn:aws:dynamodb:us-west-2:123456789012:table/Thread"` ; "provide both the table and index ARNs in the Resource field of a given Statement" | 2026-11-08 | VERIFIED |
|
|
164
|
+
| DP-E334 | Encryption at rest always on; LSI/GSI use the base table key (encryption.md:1-5 (file lines 174-178 in concat)) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | All table data is encrypted: "Server-side encryption at rest is enabled on all DynamoDB table data and cannot be disabled." ; "Local secondary indexes and global secondary indexes are encrypted using the same key as the base table." | 2026-11-08 | VERIFIED |
|
|
165
|
+
| DP-E335 | Three key choices: AWS-owned (default, no charge), AWS-managed `alias/aws/dynamodb` (KMS charges), customer-managed (KMS charges) (encryption.md:10-14) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/EncryptionAtRest.html | DynamoDB encryption at rest: "AWS owned key – Default encryption type. The key is owned by DynamoDB (no additional charge). AWS managed key – The key is stored in your account and is managed by AWS KMS (AWS KMS charges apply)." | 2026-11-08 | VERIFIED |
|
|
166
|
+
| DP-E336 | AWS-managed key: AWS controls policy; you can view policy and audit in CloudTrail (encryption.md:12) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Encryption types / Authorizing use of your KMS key: "Because the AWS managed key is in your account, you can view its policies and grants. But, because it is managed by AWS, you cannot change the policies." | 2026-11-08 | VERIFIED |
|
|
167
|
+
| DP-E337 | Customer-managed key must be symmetric; you control policy, grants, rotation (encryption.md:13,46) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Using KMS keys and data keys: "DynamoDB supports only symmetric KMS keys. You cannot use an asymmetric KMS key to encrypt your DynamoDB tables." | 2026-11-08 | VERIFIED |
|
|
168
|
+
| DP-E338 | KMS op not performed for every item access because table keys are cached (encryption.md:20-21) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Table key caching: "To avoid calling AWS KMS for every DynamoDB operation, DynamoDB caches the plaintext table keys for each caller in memory." | 2026-11-08 | VERIFIED |
|
|
169
|
+
| DP-E339 | CFN `SSESpecification.SSEEnabled`: false/omitted = AWS-owned; true = AWS-managed key; `SSEType: KMS`; `KMSMasterKeyId` only if different from alias/aws/dynamodb (encryption.md:28-43; assets/table.cfn.yaml (no SSESpecification)) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-dynamodb-table-ssespecification.html | Properties: "If enabled (true), server-side encryption type is set to KMS and an AWS managed key is used (AWS KMS charges apply). If disabled (false) or not specified, server-side encryption is set to AWS owned key." | 2026-11-08 | VERIFIED |
|
|
170
|
+
| DP-E340 | `KMSMasterKeyId` accepts a key ARN (`!Ref KmsKeyArn` parameter) (encryption.md:43-45) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-dynamodb-table-ssespecification.html | Properties (KMSMasterKeyId): "To specify a key, use its key ID, Amazon Resource Name (ARN), alias name, or alias ARN." | 2026-11-08 | VERIFIED |
|
|
171
|
+
| DP-E341 | Alias is resolved when set; retargeting alias does not switch the table key (encryption.md:60-64) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Using KMS keys and data keys (Note): "If you later change the alias to point to a different KMS key, the table continues to use the originally resolved KMS key" | 2026-11-08 | VERIFIED |
|
|
172
|
+
| DP-E342 | CLI `create-table --sse-specification Enabled=true,SSEType=KMS[,KMSMasterKeyId=...]`; AWS-owned = no override (encryption.md:73-96) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.tutorial.html | Specifying the encryption key for a new table: "--sse-specification Enabled=true,SSEType=KMS,KMSMasterKeyId=abcd1234-abcd-1234-a123-ab1234a1b234" ; "This table is now encrypted using the default AWS owned key" (no SSE option) | 2026-11-08 | VERIFIED |
|
|
173
|
+
| DP-E343 | `update-table --sse-specification` switches between keys; `Enabled=false` switches to AWS-owned, still encrypted (encryption.md:100-114) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.tutorial.html | Updating an encryption key: "aws dynamodb update-table --table-name Music --sse-specification Enabled=false Note This table is now encrypted using the default AWS owned key in the DynamoDB service account." | 2026-11-08 | VERIFIED |
|
|
174
|
+
| DP-E344 | `describe-table` shows SSEDescription (Status, KMSMasterKeyArn); `SSEType=KMS` for both managed and CMK; completion = Status ENABLED with new ARN; absent SSEDescription = AWS-owned (encryption.md:116-129) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Encryption types: "The process will be complete when the table's SSEDescription Status is ENABLED and the KMSMasterKeyArn of the new customer managed key is displayed." ; "In the Amazon DynamoDB API, the encryption type is KMS when you us | 2026-11-08 | VERIFIED |
|
|
175
|
+
| DP-E345 | AWS-managed key `alias/aws/dynamodb` may not exist until first use (encryption.md:125) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | (searched): No sentence found on this page or the encryption pages fetched about creation timing of the alias. | 2026-11-08 | UNVERIFIED |
|
|
176
|
+
| DP-E346 | KMS key policy/grants must authorize DynamoDB; required permissions incl. CreateGrant; ViaService (encryption.md:136-139) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Key policy for a customer managed key: "At a minimum, DynamoDB requires the following permissions on a customer managed key: kms:Encrypt kms:Decrypt kms:ReEncrypt* ... kms:GenerateDataKey* ... kms:DescribeKey kms:CreateGrant" | 2026-11-08 | VERIFIED |
|
|
177
|
+
| DP-E347 | Old on-demand backups keep their original key and need it to restore; keep original key enabled during transition (encryption.md:140-143) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Encryption types: "Any existing on-demand backups remain encrypted with the customer managed key that was used when those backups were created. You will need that same key to restore those backups." | 2026-11-08 | VERIFIED |
|
|
178
|
+
| DP-E348 | Auto rotation of same KMS key is not switching ARN (encryption.md:143-145). Note: partially supported | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Using KMS keys and data keys: "You can enable and disable the KMS key, enable and disable automatic key rotation, and delete the KMS key" (customer managed key features); the "not a different ARN" statement is KMS semantics, not on page | 2026-11-08 | UNVERIFIED |
|
|
179
|
+
| DP-E349 | Disabling/deleting CMK or removing grants can block table access (encryption.md:148-151). Note: grants); key-deletion irrecoverability not stated on page | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Using grants to authorize DynamoDB: "if you revoke the grant on an active encrypted table, DynamoDB will not be able to protect and maintain the table." | 2026-11-08 | VERIFIED |
|
|
180
|
+
| DP-E350 | Global tables: CMK version requirement (encryption.md:151-153) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Encryption types (Note): "Customer managed keys are not supported in Global Table Version 2017. If you want to use a customer managed key in a DynamoDB Global Table, you need to upgrade the table to Global Table Version 2019" | 2026-11-08 | VERIFIED |
|
|
181
|
+
| DP-E351 | DAX does not support a customer-managed key for cluster encryption (encryption.md:153-154) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/encryption.usagenotes.html | Encryption types: "You cannot use a customer managed key with DynamoDB Accelerator (DAX) clusters." | 2026-11-08 | VERIFIED |
|
|
182
|
+
| DP-E353 | CFN `AWS::DynamoDB::Table` properties BillingMode PAY_PER_REQUEST, DeletionProtectionEnabled, TimeToLiveSpecification {AttributeName, Enabled}, PointInTimeRecoverySpecification {PointInTimeRecoveryEnabled}, GlobalSecondaryIndexes/Projection/NonKeyAttributes, KeySchema, AttributeDefinitions (provisioning.md:26-46; assets/table.cfn.yaml:10-50) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-dynamodb-table.html | Properties: "DeletionProtectionEnabled Determines if a table is protected from deletion. When enabled, the table cannot be deleted by any user or process." ; BillingMode "PAY_PER_REQUEST sets the billing mode to On-demand capacity m | 2026-11-08 | VERIFIED |
|
|
183
|
+
| DP-E354 | A named table (explicit TableName) prevents replacement updates (provisioning.md:64-65; table.cfn.yaml:11-15) | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-dynamodb-table.html | Properties (TableName): "If you specify a name, you cannot perform updates that require replacement of this resource." | 2026-11-08 | VERIFIED |
|
|
184
|
+
| DP-E355 | `DeletionPolicy: Retain` / `UpdateReplacePolicy: Retain` keep resources (provisioning.md:64). Note: not fetched | https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-attribute-deletionpolicy.html | DeletionPolicy attribute: Not fetched in this run (not a DynamoDB property; generic CFN attribute). | 2026-11-08 | UNVERIFIED |
|
|
185
|
+
| DP-E356 | `aws cloudformation deploy --template-file --stack-name --parameter-overrides --no-execute-changeset` (provisioning.md:48-62) | https://docs.aws.amazon.com/cli/latest/reference/cloudformation/deploy.html | Description / Options: "If you want to view the change set before AWS CloudFormation executes it, use the --no-execute-changeset flag." | 2026-11-08 | VERIFIED |
|
|
186
|
+
| DP-E357 | Only key attributes belong in AttributeDefinitions; keys in KeySchema must be defined there (provisioning.md:12-14; create-table.json:4-9) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/create-table.html | Options (--key-schema): "The attributes in KeySchema must also be defined in the AttributeDefinitions array." | 2026-11-08 | VERIFIED |
|
|
187
|
+
| DP-E358 | CLI `create-table --table-name --cli-input-json`; `wait table-exists`; `update-time-to-live --time-to-live-specification Enabled=true,AttributeName=expiresAt`; `update-continuous-backups --point-in-time-recovery-specification PointInTimeRecoveryEnabled=true` (provisioning.md:73-87; create-table.sh:26-32) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/update-time-to-live.html | Examples: "aws dynamodb update-time-to-live --table-name MusicCollection --time-to-live-specification Enabled=true, AttributeName=ttl" ; update-continuous-backups: "Shorthand Syntax: PointInTimeRecoveryEnabled=boolean, RecoveryPer | 2026-11-08 | VERIFIED |
|
|
188
|
+
| DP-E359 | create-table input JSON keys BillingMode, DeletionProtectionEnabled, AttributeDefinitions, KeySchema, GlobalSecondaryIndexes, LocalSecondaryIndexes, Projection{ProjectionType,NonKeyAttributes}; ProjectionType INCLUDE (create-table.json:2-3,10-26; create-table-with-lsi.json) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/create-table.html | Options / Synopsis: "INCLUDE - Only the specified table attributes are projected into the index. The list of projected attributes is in NonKeyAttributes." ; Synopsis includes --deletion-protection-enabled, --billing-mode, --local-secondary- | 2026-11-08 | VERIFIED |
|
|
189
|
+
| DP-E360 | LSI must share base partition key; LSI only at create time (no add/delete on existing table) (create-table-with-lsi.json:28-39; aws-cli.md:164-165 (file 274-277)) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/create-table.html | Options (--local-secondary-indexes): "The key schema must begin with the same partition key as the table." (create-time-only: update-table synopsis has no LSI option; synopsis checked) | 2026-11-08 | VERIFIED |
|
|
190
|
+
| DP-E361 | TTL may report ENABLING before ENABLED (provisioning.md:97-98; aws-cli.md:306). Note: not fetched | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/describe-time-to-live.html | Output (TimeToLiveStatus): Not fetched in this run. | 2026-11-08 | UNVERIFIED |
|
|
191
|
+
| DP-E362 | GetItem requires full key; strong consistency optional on base table, `--consistent-read`; `--return-consumed-capacity` (aws-cli.md:63-65 (file 174-175)) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/get-item.html | Options: "--consistent-read / --no-consistent-read (boolean) Determines the read consistency model: If set to true, then the operation uses strongly consistent reads; otherwise, the operation uses eventually consistent reads." | 2026-11-08 | VERIFIED |
|
|
192
|
+
| DP-E363 | Strongly consistent reads not supported on GSI; allowed on table/LSI (aws-cli.md:65,90 (file 175,200-208)) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/query.html | Description: "Global secondary indexes support eventually consistent reads only, so do not specify ConsistentRead when querying a global secondary index." ; "For a query on a table or on a local secondary index, you can set the Consi | 2026-11-08 | VERIFIED |
|
|
193
|
+
| DP-E364 | Query page stops at 1 MB; `--no-paginate` = single call; `--max-items`/`--starting-token`/NextToken is the CLI layer, distinct from LastEvaluatedKey/ExclusiveStartKey (aws-cli.md:82-87 (file 192-197)) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/query.html | Description; Options: "A single Query operation will read up to the maximum number of items set (if using the Limit parameter) or a maximum of 1 MB of data" ; "--no-paginate ... the AWS CLI will only make one call, for the first page of result… | 2026-11-08 | VERIFIED |
|
|
194
|
+
| DP-E365 | Query flags `--exclusive-start-key`, `--limit`, `--scan-index-forward/--no-scan-index-forward`, `--no-consistent-read`, `--return-consumed-capacity INDEXES`, `--index-name`, `--key-condition-expression` (aws-cli.md:76-80 (file 186-189)) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/query.html | Options: "--scan-index-forward / --no-scan-index-forward (boolean) Specifies the order for index traversal: If true (default), the traversal is performed in ascending order; if false, the traversal is performed in descending orde | 2026-11-08 | VERIFIED |
|
|
195
|
+
| DP-E366 | Filter expressions / projection expressions do not reduce consumed units (aws-cli.md:115-116 (file 225-226)). Note: filter applied after read); projection part UNVERIFIED | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/query.html | Description: "FilterExpression is applied after a Query finishes, but before the results are returned." (reads are already charged; explicit "no unit reduction" sentence not located on this page) | 2026-11-08 | VERIFIED |
|
|
196
|
+
| DP-E367 | put-item `--condition-expression`; update-item with `SET ... REMOVE`; `--expression-attribute-names/values` (aws-cli.md:131-137 (file 241-247)). Note: not fetched | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/update-item.html | Options: Not fetched in this run (flag names are standard; PutItem/UpdateItem pages cited by file). | 2026-11-08 | UNVERIFIED |
|
|
197
|
+
| DP-E368 | `create-table` alt with LSI asset, then `wait table-exists` (aws-cli.md:157-164 (file 267-275)). Note: not fetched | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/wait/table-exists.html | Description: Not fetched in this run. | 2026-11-08 | UNVERIFIED |
|
|
198
|
+
| DP-E369 | `update-table --attribute-definitions --global-secondary-index-updates '[{"Create":{IndexName,KeySchema,Projection}}]'` adds a GSI (aws-cli.md:169-182 (file 279-290)) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/update-table.html | Options: "--global-secondary-index-updates (list) An array of one or more global secondary indexes for the table. For each index in the array, you can request one action: Create - add a new global secondary index to the table." | 2026-11-08 | VERIFIED |
|
|
199
|
+
| DP-E370 | describe-table exposes GSI `IndexStatus` (ACTIVE) and `Backfilling`; do not route reads until ACTIVE and backfill done (aws-cli.md:182-186 (file 288-295)) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/create-table.html | Output (GlobalSecondaryIndexes): "IndexStatus -> (string) The current state of the global secondary index: ... ACTIVE - The index is ready for use." ; "Backfilling -> (boolean) Indicates whether the index is currently backfilling." | 2026-11-08 | VERIFIED |
|
|
200
|
+
| DP-E371 | TTL is delayed cleanup, not an exact expiry (aws-cli.md:195-200 (file 305-310)). Note: not fetched | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/howitworks-ttl.html | How TTL works: Not fetched in this run. | 2026-11-08 | UNVERIFIED |
|
|
201
|
+
| DP-E372 | CLI flags `--cli-input-json file://`, `describe-time-to-live`, `describe-continuous-backups`, existing name yields ResourceInUseException (create-table.sh:15,26-37). Note: cited page is PutResourcePolicy errors, not CreateTable/CLI; flags not confirmed | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutResourcePolicy.html | Errors: "ResourceInUseException The operation conflicts with the resource's availability. For example: You attempted to recreate an existing table." | 2026-11-08 | UNVERIFIED |
|
|
202
|
+
| DP-E373 | PITR specification fields `PointInTimeRecoveryEnabled` (+ optional RecoveryPeriodInDays default 35) (provisioning.md:99-101 (PITR)) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/update-continuous-backups.html | Options: "If no value is provided, the value will default to 35." (RecoveryPeriodInDays, min 1 max 35) | 2026-11-08 | VERIFIED |
|
|
203
|
+
| DP-E401 | PITR recovery period configurable 1-35 days (references/recovery-and-replicas.md:17; commands/backup/pitr.md:14,22) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html | Recovery Period: You can set the recovery period for continuous backups to be any number between 1 and 35 days. | 2026-11-08 | VERIFIED |
|
|
204
|
+
| DP-E402 | LatestRestorableDateTime typically ~5 minutes behind now (recovery-and-replicas.md:19; backup/pitr.md:15) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html | Point-in-time recovery: how it works: LatestRestorableDateTime is typically five minutes before the current time. | 2026-11-08 | VERIFIED |
|
|
205
|
+
| DP-E403 | ContinuousBackupsStatus=ENABLED alone does not establish PITR enablement (recovery-and-replicas.md:20; backup/pitr.md:14) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html | Enable PITR: An ENABLED value doesn't mean that point-in-time recovery is turned on. | 2026-11-08 | VERIFIED |
|
|
206
|
+
| DP-E404 | Disabling/re-enabling PITR resets recoverable history (recovery-and-replicas.md:21; backup/pitr.md:39) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/pointintimerecovery_restores.html | Restoring a table using point-in-time recovery: If you disable point-in-time recovery and later enable it on a table, you reset the start time for which you can recover that table. | 2026-11-08 | VERIFIED |
|
|
207
|
+
| DP-E405 | Increasing window creates no earlier history; reducing removes older recoverability (backup/pitr.md:16-17; recovery-and-replicas.md:20-21) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html | Edit PITR: If you change the recovery period and decrease it to a value lower than previously set... any continuous backups that fall outside of the new set value will not be recoverable. | 2026-11-08 | VERIFIED |
|
|
208
|
+
| DP-E406 | Reducing retention window does not reduce PITR price (recovery-and-replicas.md:22). Note: page states it affirmatively; skill wording "not documented to" is weaker than the doc | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html | Point-in-time recovery: how it works: Changing the recovery window (for example, from 35 days to 1 day) doesn't reduce the price. | 2026-11-08 | VERIFIED |
|
|
209
|
+
| DP-E407 | update-continuous-backups takes PointInTimeRecoveryEnabled and RecoveryPeriodInDays (recovery-and-replicas.md:29-30; backup/pitr.md:32-33) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html | Enable PITR: PointInTimeRecoverySpecification= { 'PointInTimeRecoveryEnabled': True, 'RecoveryPeriodInDays': 35 } | 2026-11-08 | VERIFIED |
|
|
210
|
+
| DP-E408 | restore-table-to-point-in-time uses --restore-date-time or --use-latest-restorable-time (skill: use one instead of the other, never combine) (recovery-and-replicas.md:36,46; restore/pitr.md:33-38). Note: for flag names; the "never combine" rule is not stated on the page (see DP-E409 | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.Tutorial.html | Restoring a table to a point in time: You can also restore to a specific point in time. To do this, run the command using the --restore-date-time argument, and specify a timestamp. | 2026-11-08 | VERIFIED |
|
|
211
|
+
| DP-E409 | Timestamp and latest flags are mutually exclusive (restore/pitr.md:32,38). Note: no sentence found that says combining is rejected; searched Tutorial and API_RestoreTableToPointInTime | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.Tutorial.html | Restoring a table to a point in time: Specifying the --no-use-latest-restorable-time argument is optional when restoring to a specific point in time. | 2026-11-08 | UNVERIFIED |
|
|
212
|
+
| DP-E410 | PITR/backup restore always creates a NEW table (recovery-and-replicas.md:51,24; restore.md:42; restore/*.md) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html | Enable PITR: The point-in-time recovery process always restores to a new table. | 2026-11-08 | VERIFIED |
|
|
213
|
+
| DP-E411 | Must re-establish tags, IAM policy, PITR, TTL, Streams, auto scaling, Contributor Insights, alarms after restore (recovery-and-replicas.md:68-70; restore.md:62) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/pointintimerecovery_restores.html | Restoring a table using point-in-time recovery: You must manually set the following on the restored table: Auto scaling policies AWS Identity and Access Management policies Amazon CloudWatch Events metrics and alarms CloudWatch Contributor Insights settings Tags Strea | 2026-11-08 | VERIFIED |
|
|
214
|
+
| DP-E412 | Restored table is independent, incl. from a global-table replica; replica topology is not restored (recovery-and-replicas.md:52-54; restore.md:67). Note: searched pointintimerecovery_restores, PointInTimeRecovery.Tutorial, Howitworks, API_RestoreTableToPointInTime, API_RestoreTableFromBackup | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/pointintimerecovery_restores.html | Restoring a table using point-in-time recovery: (no sentence about global tables / replicas found on the PITR or RestoreTable pages) | 2026-11-08 | UNVERIFIED |
|
|
215
|
+
| DP-E413 | Deleting a table with PITR enabled creates a SYSTEM backup retained 35 days that restores pre-deletion state (restore.md:27-30; recovery-target.md:13-15) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html | Delete a table with PITR enabled: DynamoDB automatically creates a backup snapshot called a system backup and retains it for 35 days (at no additional cost). | 2026-11-08 | VERIFIED |
|
|
216
|
+
| DP-E414 | BackupType SYSTEM semantics in DescribeBackup (restore.md:76 (cited)) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/describe-backup.html | Output / BackupType: SYSTEM - If you delete a table with point-in-time recovery enabled, a SYSTEM backup is automatically created and is retained for 35 days (at no additional cost). | 2026-11-08 | VERIFIED |
|
|
217
|
+
| DP-E415 | RestoreTableFromBackup creates a new table from a backup ARN (--backup-arn, --target-table-name) (restore/on-demand.md:22; restore.md:3-4). Note: params BackupArn and TargetTableName both "Required: Yes" | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_RestoreTableFromBackup.html | RestoreTableFromBackup: Creates a new table from an existing backup. | 2026-11-08 | VERIFIED |
|
|
218
|
+
| DP-E701 | A backup records the TableId of the table it was created from (SourceTableDetails.TableId, required) (commands/restore/on-demand.md) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_SourceTableDetails.html | SourceTableDetails: "Unique identifier for the table for which the backup was created." | 2026-11-08 | VERIFIED |
|
|
219
|
+
| DP-E702 | DescribeTable returns a TableId that DynamoDB generates when the table is created, so a recreated table with the same name gets a new TableId; the field is optional, so a missing value must fail closed (commands/restore/on-demand.md) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_TableDescription.html | TableDescription: "A unique identifier for the table, in UUID format, generated by DynamoDB when the table is created." | 2026-11-08 | VERIFIED |
|
|
220
|
+
| DP-E416 | CreateBackup is asynchronous; changes within +/-1 minute of request may or may not be included; no causal consistency (backup/on-demand.md:7-10) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_CreateBackup.html | CreateBackup: If you submit a backup request on 2018-12-14 at 14:25:00, the backup is guaranteed to contain all data committed to the table up to 14:24:00, and data committed after 14:26:00 will not be. | 2026-11-08 | VERIFIED |
|
|
221
|
+
| DP-E417 | create-backup takes --table-name/--backup-name; response BackupDetails.BackupArn; describe-backup returns BackupDescription with SourceTableDetails.TableArn and BackupStatus AVAILABLE (backup/on-demand.md:14-26; restore/on-demand.md:12-19). Note: BackupStatus value AVAILABLE from describe-backup CLI page: "Possible values: CREATING DELETED AVAILABLE" | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_CreateBackup.html | Request/Response Syntax: { " BackupName ": " string ", " TableName ": " string " } ... " BackupDetails ": { " BackupArn ": " string " | 2026-11-08 | VERIFIED |
|
|
222
|
+
| DP-E418 | Native on-demand backup does not require PITR to be enabled (backup.md:21-22). Note: searched CreateBackup, Restore.Tutorial | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_CreateBackup.html | CreateBackup: (no sentence stating PITR is or is not a prerequisite) | 2026-11-08 | UNVERIFIED |
|
|
223
|
+
| DP-E419 | Current-version replicas are added with UpdateTable (--replica-updates Create RegionName); MREC starts from an existing populated table (recovery-and-replicas.md:80-83,96-97). Note: CLI shape: tutorial shows `--replica-updates '[ { "Create": { "RegionName": "us-east-1"}}]'` and `MultiRegionConsistency` in describe-table query on DDB/V2globaltables.tutorial.html | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Multi-Region eventual consistency (MREC): You create a MREC global table by adding a replica to an existing DynamoDB table. | 2026-11-08 | VERIFIED |
|
|
224
|
+
| DP-E420 | Use current (not legacy) global tables version (recovery-and-replicas.md:81) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Versions: You should use Version 2019.11.21 (Current) whenever possible. | 2026-11-08 | VERIFIED |
|
|
225
|
+
| DP-E421 | Replica creation needs UpdateTable on source; destination needs CreateTable, CreateTableReplica, Query, Scan, UpdateItem, PutItem, GetItem, DeleteItem, BatchWriteItem (recovery-and-replicas.md:110-113). Note: destination list on same page: dynamodb:CreateTable, CreateTableReplica, Query, Scan, UpdateItem, PutItem, GetItem, DeleteItem, BatchWriteItem | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables-security.html | Permissions for creating global tables: To create a global table or add a replica using the UpdateTable API, you must have the following permission on the source table resource: dynamodb:UpdateTable | 2026-11-08 | VERIFIED |
|
|
226
|
+
| DP-E422 | If replication SLR missing, creation needs iam:CreateServiceLinkedRole scoped to the service (recovery-and-replicas.md:113-114). Note: policy example scopes it to .../aws-service-role/replication.dynamodb.amazonaws.com/AWSServiceRoleForDynamoDBReplication | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables-security.html | Permissions for creating global tables: The following permission allows DynamoDB to create this role automatically when you create a global table for the first time: iam:CreateServiceLinkedRole | 2026-11-08 | VERIFIED |
|
|
227
|
+
| DP-E423 | MREC asynchronous, per-item conflict resolution; strong reads can miss other-Region writes (recovery-and-replicas.md:118-119) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Multi-Region eventual consistency (MREC): Strongly consistent read operations return the latest version of an item if that item was last updated in the Region where the read occurred, but may return stale data if the item was last updated in a different Region. | 2026-11-08 | VERIFIED |
|
|
228
|
+
| DP-E424 | Transactions do not replicate as an atomic group (recovery-and-replicas.md:119-120) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Transactions: Transactional writes are not replicated as a unit across Regions, meaning only some of the writes in a transaction might be returned by read operations in other replicas at a given point in time. | 2026-11-08 | VERIFIED |
|
|
229
|
+
| DP-E425 | TTL sync; replicated-delete charges in other Regions (recovery-and-replicas.md:120) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Time To Live (TTL): However, you are charged for the replicated delete in each other region with a replica in the global table. | 2026-11-08 | VERIFIED |
|
|
230
|
+
| DP-E426 | PITR, tags, deletion protection, resource policies are not replicated; verify per Region (recovery-and-replicas.md:121-123) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Settings synchronization: The following settings are never synchronized between replicas: Deletion protection Point-in-time Recovery Tags Table CloudWatch Contributor Insights enablement ... Resource Policies | 2026-11-08 | VERIFIED |
|
|
231
|
+
| DP-E427 | A settings-replication mode field can be inspected (recovery-and-replicas.md:123-124). Note: field exists in TableDescription; its semantics not read | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_RestoreTableToPointInTime.html | Response Elements (TableDescription): " GlobalTableSettingsReplicationMode ": " string " | 2026-11-08 | VERIFIED |
|
|
232
|
+
| DP-E428 | DAX caches are not updated by replicated writes (regional, stale until TTL) (recovery-and-replicas.md:125; streams-and-dax.md:~101-102) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | DynamoDB Accelerator (DAX): Writes to global table replicas bypass DynamoDB Accelerator (DAX), updating DynamoDB directly. As a result, DAX caches can become stale as writes are not updating the DAX cache. | 2026-11-08 | VERIFIED |
|
|
233
|
+
| DP-E429 | MRSC needs exactly three Regions (three replicas or two plus witness) (recovery-and-replicas.md:129-130) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Multi-Region strong consistency (MRSC): A MRSC global table must be deployed in exactly three Regions. You can configure a MRSC global table with three replicas, or with two replicas and one witness. | 2026-11-08 | VERIFIED |
|
|
234
|
+
| DP-E430 | MRSC requires empty starting table, no writes during conversion (recovery-and-replicas.md:130) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Multi-Region strong consistency (MRSC): Converting a single-Region table to a MRSC global table with existing items is not supported. Make sure that no data is written into the table during the conversion process. | 2026-11-08 | VERIFIED |
|
|
235
|
+
| DP-E431 | MRSC mode cannot change after creation; no additional replicas can be added (recovery-and-replicas.md:130-131) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Consistency modes / MRSC: You cannot change a global table's consistency mode after creation. ... You cannot add additional replicas to an existing MRSC global table. | 2026-11-08 | VERIFIED |
|
|
236
|
+
| DP-E432 | MRSC: TTL and LSI unsupported, GSI reads eventual (recovery-and-replicas.md:131-132) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Multi-Region strong consistency (MRSC): Time to Live (TTL) is not supported for MRSC global tables. Local secondary indexes (LSIs) are not supported for MRSC global tables. ... reads from a GSI are eventually consistent. | 2026-11-08 | VERIFIED |
|
|
237
|
+
| DP-E433 | MRSC: transaction APIs unsupported (recovery-and-replicas.md:132) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Transactions: Global tables configured for multi-Region strong consistency (MRSC) do not support transaction operations, and will return an error if those operations are invoked on an MRSC replica. | 2026-11-08 | VERIFIED |
|
|
238
|
+
| DP-E434 | Witness creation has its own permissions (recovery-and-replicas.md:133) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables-security.html | Additional permissions for MRSC global tables using a witness: Additional permissions for MRSC global tables using a witness | 2026-11-08 | VERIFIED |
|
|
239
|
+
| DP-E435 | MRSC eligible Regions may span continents (recovery-and-replicas.md:135-136). Note: the skill's side claim that "some best-practices pages retain an older restriction" was not checked; UNVERIFIED | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Multi-Region strong consistency (MRSC): An MRSC global table can include replicas from any combination of three of these Regions, including Regions on different continents. | 2026-11-08 | VERIFIED |
|
|
240
|
+
| DP-E436 | Multi-account global tables have a different contract (separate accounts, settings not overridable, MREC only) (recovery-and-replicas.md:139-140) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_MA_HowItWorks.html | How DynamoDB global tables work (multi-account): Multi-account replication is supported for multi-Region eventual consistency (MREC) global tables. | 2026-11-08 | VERIFIED |
|
|
241
|
+
| DP-E437 | Streams retains records for 24 hours (streams-and-dax.md:21) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html | Change data capture for DynamoDB Streams: stores this information in a log for up to 24 hours. | 2026-11-08 | VERIFIED |
|
|
242
|
+
| DP-E438 | StreamViewType values KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, NEW_AND_OLD_IMAGES; --stream-specification StreamEnabled/StreamViewType (streams-and-dax.md:19-20) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html | Enabling a stream: StreamViewType — Specifies the information that will be written to the stream whenever data in the table is modified: KEYS_ONLY ... NEW_IMAGE ... OLD_IMAGE ... NEW_AND_OLD_IMAGES | 2026-11-08 | VERIFIED |
|
|
243
|
+
| DP-E439 | Ordering is per item, not across items with the same partition key (streams-and-dax.md:21-22) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html | Reading and processing a stream: DynamoDB Streams guarantees ordering at the level of an individual item... not across an entire partition. | 2026-11-08 | VERIFIED |
|
|
244
|
+
| DP-E440 | Lambda delivery is at least once (streams-and-dax.md:22-23) | https://docs.aws.amazon.com/lambda/latest/dg/with-ddb.html | Polling and batching streams: Lambda event source mappings process each event at least once, and duplicate processing of records can occur. | 2026-11-08 | VERIFIED |
|
|
245
|
+
| DP-E441 | Changing image type requires disable/re-enable and creates a new stream ARN (streams-and-dax.md:27-28). Note: new ARN: "If you disable and then re-enable a stream on the table, a new stream is created with a different stream descriptor." | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html | Enabling a stream: It is not possible to edit a StreamViewType once a stream has been setup. If you need to make changes... you must disable the current stream and create a new one. | 2026-11-08 | VERIFIED |
|
|
246
|
+
| DP-E442 | MREC replication stream cannot be disabled (streams-and-dax.md:29-30) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Streams: Streams are therefore enabled by default on all replicas in an MREC global table, and cannot be disabled on those replicas. | 2026-11-08 | VERIFIED |
|
|
247
|
+
| DP-E443 | Process parent shards before children; follow lineage (streams-and-dax.md:44-47) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html | Reading and processing a stream: an application must always process a parent shard before it processes a child shard. | 2026-11-08 | VERIFIED |
|
|
248
|
+
| DP-E444 | Iterator types TRIM_HORIZON oldest / LATEST newest; dynamodbstreams CLI flags (streams-and-dax.md:50-51 (TRIM_HORIZON/LATEST), 52-55 (CLI get-shard-iterator, describe-stream --limit/--no-paginate, get-records --limit)). Note: CLI examples page not fetched; only API-level wording found | https://docs.aws.amazon.com/code-library/latest/ug/cli_2_dynamodb-streams_code_examples.html | n/a: (not fetched; Streams.html only says GetShardIterator can give "the oldest point, the newest point, or a particular point") | 2026-11-08 | UNVERIFIED |
|
|
249
|
+
| DP-E445 | IAM actions are dynamodb:DescribeStream/GetShardIterator/GetRecords on stream ARN; ListStreams has no resource-level scope; UpdateTable enables streams (streams-and-dax.md:67-69). Note: API action names confirmed, but IAM action names/resource types not: Service Authorization Reference pages are JS-rendered and returned no text; iam-policy-example-data-stream pages returned empty | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html | Reading and processing a stream: ListStreams — Returns a list of stream descriptors for the current account and endpoint. | 2026-11-08 | UNVERIFIED |
|
|
250
|
+
| DP-E446 | Mapping setup needs lambda:CreateEventSourceMapping; iam:PassRole only for creating/changing the function execution role (streams-and-dax.md:74-77). Note: lambda-api-permissions-ref and with-ddb fetched; no PassRole / CreateEventSourceMapping text extracted | https://docs.aws.amazon.com/lambda/latest/dg/with-ddb.html | n/a: (no sentence found) | 2026-11-08 | UNVERIFIED |
|
|
251
|
+
| DP-E447 | AWSLambdaDynamoDBExecutionRole is the managed policy for reading the stream (streams-and-dax.md:81-82) | https://docs.aws.amazon.com/lambda/latest/dg/services-dynamodb-eventsourcemapping.html | Permissions: This is an AWS managed policy that contains the permissions your function needs to read from the DynamoDB stream. | 2026-11-08 | VERIFIED |
|
|
252
|
+
| DP-E448 | DAX item cache covers GetItem/BatchGetItem; writes via DAX update item cache (streams-and-dax.md:101) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.consistency.html | DAX item cache behavior: In addition to GetItem, the DAX client also supports BatchGetItem requests. ... DAX updates the items in its item cache, regardless of the TTL value for these items. | 2026-11-08 | VERIFIED |
|
|
253
|
+
| DP-E449 | Query/Scan cache not invalidated by writes, even through DAX (streams-and-dax.md:103-104) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.consistency.html | DAX query cache behavior: Updates to the item cache, or to the underlying DynamoDB table, do not invalidate or modify the results stored in the query cache. | 2026-11-08 | VERIFIED |
|
|
254
|
+
| DP-E450 | Strong and transactional reads pass through and are not cached (streams-and-dax.md:105). Note: TransactGetItems: "DAX handles TransactGetItems requests the same way it handles strongly consistent reads." | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.consistency.html | Strongly consistent and transactional reads: DAX passes strongly consistent read requests to DynamoDB. ... DAX returns the results to the client, but it does not cache the results. | 2026-11-08 | VERIFIED |
|
|
255
|
+
| DP-E451 | A GSI cannot become strongly consistent through DAX (streams-and-dax.md:105-106) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.consistency.html | Strongly consistent and transactional reads: (no GSI sentence found) | 2026-11-08 | UNVERIFIED |
|
|
256
|
+
| DP-E452 | Item TTL=0 and query TTL=0 mean different things (streams-and-dax.md:106-108) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.concepts.html | Item cache / Query cache: If you specify zero as the item cache TTL setting, items in the item cache will only be refreshed due to an LRU eviction or a "write-through" operation. ... If you specify zero as the query cache TTL setting, the query r | 2026-11-08 | VERIFIED |
|
|
257
|
+
| DP-E453 | AWS documents DAX clients for Java, .NET, Node.js, Python and Go (corrected: an earlier version omitted .NET) (streams-and-dax.md:109-112) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.client.run-application-dotnet.html | .NET and DAX: It works with the AWS SDK v4 for .NET. | 2026-11-08 | VERIFIED |
|
|
258
|
+
| DP-E454 | Recommended HA: three nodes (streams-and-dax.md:120-122) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.consistency.html | Consistency among DAX cluster nodes: we recommend that you provision your DAX cluster with at least three nodes. | 2026-11-08 | VERIFIED |
|
|
259
|
+
| DP-E455 | dax create-cluster flags: --node-type, --replication-factor, --subnet-group-name, --security-group-ids, --iam-role-arn, --sse-specification Enabled=, --cluster-endpoint-encryption-type TLS (streams-and-dax.md:134-138). Note: all other flags present; replication-factor, node-type, iam-role-arn marked [required]; "DAX clusters can only run in an Amazon VPC environment." | https://docs.aws.amazon.com/cli/latest/reference/dax/create-cluster.html | Options: --cluster-endpoint-encryption-type (string) The type of encryption the cluster's endpoint should support. Values are: NONE for no encryption TLS for Transport Layer Security | 2026-11-08 | VERIFIED |
|
|
260
|
+
| DP-E456 | Caller rights dax:GetItem/dax:Query target the cluster ARN; service role trusts dax.amazonaws.com and holds DynamoDB rights separately (streams-and-dax.md:142-143). Note: trust `"Service": "dax.amazonaws.com"` and `dax:GetItem ... Resource arn:aws:dax:...:cache/DAXCluster01` on same page | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.access-control.html | DAX service role / access to DAX: The policy document allows access to the DAX cluster, but it does not grant any DynamoDB permissions. (The DynamoDB permissions are conferred by the DAX service role.) | 2026-11-08 | VERIFIED |
|
|
261
|
+
| DP-E457 | Setup needs dax:CreateCluster and iam:PassRole on the exact role (streams-and-dax.md:143-144). Note: SAR pages JS-rendered | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.access-control.html | n/a: (no CreateCluster / PassRole sentence found) | 2026-11-08 | UNVERIFIED |
|
|
262
|
+
| DP-E458 | DAX cluster encryption is separate from table KMS; table CMK does not give cluster CMK support (streams-and-dax.md:149-150) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAXEncryptionAtRest.html | DAX encryption at rest: Customer-specified AWS KMS keys are not supported. | 2026-11-08 | VERIFIED |
|
|
263
|
+
| DP-E501 | ConsumedRead/WriteCapacityUnits: TableName only excludes GSIs; add GlobalSecondaryIndexName for a GSI; Sum / seconds = rate (references/monitoring.md:26) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | ConsumedReadCapacityUnits: "The `TableName` dimension returns the `ConsumedReadCapacityUnits` for the table, but not for any global secondary indexes." / "get the `Sum` value over a span of one minute, and divide it by the number of seconds in a m | 2026-11-08 | VERIFIED |
|
|
264
|
+
| DP-E502 | Read/WriteThrottleEvents: TableName + GlobalSecondaryIndexName, Sum; batch partial throttling not in table-level view (references/monitoring.md:27) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | ReadThrottleEvents: "The `ThrottledRequests` metric for the entire `BatchGetItem` is not incremented unless *all 10* of the `GetItem` events are throttled." / "Dimensions: `TableName`, `GlobalSecondaryIndexName`" | 2026-11-08 | VERIFIED |
|
|
265
|
+
| DP-E503 | ThrottledRequests and SystemErrors need TableName AND Operation; SystemErrors with TableName only is not the series (references/monitoring.md:28) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | SystemErrors: "DynamoDB publishes `SystemErrors` only on the `TableName` and `Operation` dimension pair. It does not publish this metric on `TableName` alone." (ThrottledRequests: "Dimensions: `TableName, Operation`") | 2026-11-08 | VERIFIED |
|
|
266
|
+
| DP-E504 | SuccessfulRequestLatency: TableName + Operation; Average or percentiles; excludes client/network/retry time (references/monitoring.md:29, :54 ; commands/performance-test.md:48) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | SuccessfulRequestLatency: "`SuccessfulRequestLatency` reflects activity only within DynamoDB or Amazon DynamoDB Streams, and doesn't consider network latency or client-side activity." (Valid Statistics include `Percentile`; Dimensions: `TableName | 2026-11-08 | VERIFIED |
|
|
267
|
+
| DP-E505 | UserErrors is a Regional/account aggregate with no table dimension (references/monitoring.md:30) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | UserErrors: "`UserErrors` represents the aggregate of HTTP 400 errors for DynamoDB or Amazon DynamoDB Streams requests for the current AWS Region and the current AWS account." | 2026-11-08 | VERIFIED |
|
|
268
|
+
| DP-E506 | OnlineIndexPercentageProgress / OnlineIndexThrottleEvents use table/index dimensions (references/monitoring.md:31) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | OnlineIndexPercentageProgress: "Dimensions: `TableName, GlobalSecondaryIndexName`" (note: OnlineIndexThrottleEvents page text: "This metric is expected to show 0 during index builds.") | 2026-11-08 | VERIFIED |
|
|
269
|
+
| DP-E507 | CLI: `cloudwatch get-metric-statistics` with --statistics Sum and --extended-statistics p99, --start-time/--end-time/--period/--dimensions (references/monitoring.md:44-57) | https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/get-metric-statistics.html | Options: "When calling `GetMetricStatistics`, you must specify either `Statistics` or `ExtendedStatistics`, but not both." (options --extended-statistics, --statistics, --period, --dimensions present in Synopsis) | 2026-11-08 | VERIFIED |
|
|
270
|
+
| DP-E508 | `--no-paginate`, `--no-cli-pager`, `--output`, `--query`, `--profile`, `--region` CLI flags (references/monitoring.md:42,16) | https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/get-metric-statistics.html | Global Options: "`--no-paginate` (boolean) Disable automatic pagination. If automatic pagination is disabled, the AWS CLI will only make one call, for the first page of results." | 2026-11-08 | VERIFIED |
|
|
271
|
+
| DP-E509 | ReplicationLatency dimensions TableName + ReceivingRegion; Average/Maximum (references/monitoring.md:69) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | ReplicationLatency: "Dimensions: `TableName, ReceivingRegion` Valid Statistics: `Average` `Minimum` `Maximum`" | 2026-11-08 | VERIFIED |
|
|
272
|
+
| DP-E510 | ReplicationLatency is "queried in source Region" (references/monitoring.md:69) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Monitoring global tables: Page says only: "`ReplicationLatency` ... is emitted for every source and destination Region pair in a global table." No sentence says which Region it is queried in. | 2026-11-08 | UNVERIFIED |
|
|
273
|
+
| DP-E511 | MREC publishes ReplicationLatency; MRSC has no such metric; it is not an RPO guarantee (references/monitoring.md:69) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Monitoring global tables: "Global tables configured for multi-Region strong consistency (MRSC) do not publish a `ReplicationLatency` metric." | 2026-11-08 | VERIFIED |
|
|
274
|
+
| DP-E512 | Lambda IteratorAge (AWS/Lambda, FunctionName dimension) measures stream consumer lag (references/monitoring.md:70) | https://docs.aws.amazon.com/lambda/latest/dg/monitoring-metrics-types.html | Performance metrics: "`IteratorAge` – For DynamoDB, Kinesis, and Amazon DocumentDB event sources, the age of the last record in the event in milliseconds." ; dimension page (monitoring-metrics-view): "**By Function Name** (`FunctionName`) – | 2026-11-08 | VERIFIED |
|
|
275
|
+
| DP-E513 | DynamoDB Streams record retention is 24 hours (references/monitoring.md:70) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html | Data retention limit for DynamoDB Streams: "All data in DynamoDB Streams is subject to a 24-hour lifetime." | 2026-11-08 | VERIFIED |
|
|
276
|
+
| DP-E514 | DAX AWS/DAX ItemCacheHits/Misses, QueryCacheHits/Misses; dimensions ClusterId or ClusterId+NodeId; Sum (references/monitoring.md:71) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/dax-metrics-dimensions-dax.html | DAX Metrics / Dimensions for DAX Metrics: "ClusterId, NodeId / Limits the data to a node within a cluster." ; ItemCacheHits valid stats include `Sum` | 2026-11-08 | VERIFIED |
|
|
277
|
+
| DP-E515 | DAX emits sparse/nonzero signals (references/monitoring.md:73) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/dax-metrics-dimensions-dax.html | DAX Metrics: "DAX sends metrics to CloudWatch only when they have a non-zero value." | 2026-11-08 | VERIFIED |
|
|
278
|
+
| DP-E516 | describe-table `Table.GlobalSecondaryIndexes[].IndexStatus` ACTIVE means ready (references/monitoring.md:16-19) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_GlobalSecondaryIndexDescription.html | IndexStatus: "`ACTIVE` - The index is ready for use." (Valid Values: `CREATING / UPDATING / DELETING / ACTIVE`) | 2026-11-08 | VERIFIED |
|
|
279
|
+
| DP-E517 | put-metric-alarm flags --datapoints-to-alarm, --treat-missing-data, --actions-enabled, --alarm-actions, --comparison-operator GreaterThanThreshold (references/monitoring.md:104-109) | https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/put-metric-alarm.html | Options: "`--actions-enabled` / `--no-actions-enabled` (boolean) Indicates whether actions should be executed during any changes to the alarm state. The default is `TRUE`." ; Possible values include `GreaterThanThreshold` | 2026-11-08 | VERIFIED |
|
|
280
|
+
| DP-E518 | put-metric-alarm can overwrite an existing alarm (references/monitoring.md:94-95) | https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_PutMetricAlarm.html | Description: "When you update an existing alarm, its state is left unchanged, but the update completely overwrites the previous configuration of the alarm." | 2026-11-08 | VERIFIED |
|
|
281
|
+
| DP-E519 | Primary sources disagree: user guide says AWS/DynamoDB default is ignore with override; PutMetricAlarm API reference says always ignore (references/monitoring.md:113-121) | https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/alarms-and-missing-data.html vs https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_PutMetricAlarm.html | Configuring how CloudWatch alarms treat missing data (Important) vs TreatMissingData: User guide: "Alarms that evaluate metrics in the `AWS/DynamoDB` namespace default to ignore missing data. You can override this if you choose a different option for how the alarm should treat missing data." API ref: "Ala | 2026-11-08 | CONFLICT |
|
|
282
|
+
| DP-E520 | `ignore` keeps the alarm in its current (possibly ALARM) state on missing data (references/monitoring.md:117-119) | https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/alarms-and-missing-data.html | Configuring how CloudWatch alarms treat missing data: "`ignore` – The current alarm state is maintained" | 2026-11-08 | VERIFIED |
|
|
283
|
+
| DP-E521 | cloudwatch:ListMetrics/GetMetricStatistics/GetMetricData lack table-level ARN scoping (use Resource *) (references/monitoring.md:123-125) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazoncloudwatch.html | Actions defined by Amazon CloudWatch: Firecrawl scrape returned an empty Resource-types column for these actions, but the same scrape also returned empty for PutMetricAlarm/DescribeAlarms and reported the URL as reference.html, so the render is not trustwort | 2026-11-08 | UNVERIFIED |
|
|
284
|
+
| DP-E522 | PutMetricAlarm/DescribeAlarms use alarm resources (references/monitoring.md:126-127) | https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazoncloudwatch.html | Actions defined by Amazon CloudWatch: See DP-E521: page content not obtainable. Tags text on PutMetricAlarm page ("you must have the `cloudwatch:TagResource` permission") confirms action names only. | 2026-11-08 | UNVERIFIED |
|
|
285
|
+
| DP-E523 | Contributor Insights is opt-in (enabled per table or GSI) and has a cost impact; the page does not state that it exposes key values (monitoring.md:62-63; commands/performance-test.md:56) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/contributorinsights_HowItWorks.html | How it works: "When you enable CloudWatch Contributor Insights for DynamoDB on a table or global secondary index" | 2026-11-08 | UNVERIFIED |
|
|
286
|
+
| DP-E524 | Empty page can carry LastEvaluatedKey; only an empty/absent LastEvaluatedKey means the end (references/language-adapters.md:21-28, :183, :210 ; assets/query-pages.mjs:21-23,50) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | Response Elements / LastEvaluatedKey: "If `LastEvaluatedKey` is not empty, it does not necessarily mean that there is more data in the result set. The only way to know when you have reached the end of the result set is when `LastEvaluatedKey` is empty." and | 2026-11-08 | VERIFIED |
|
|
287
|
+
| DP-E525 | Query params ConsistentRead, ScanIndexForward=false, Limit, ReturnConsumedCapacity TOTAL, begins_with on sort key, ExpressionAttributeNames/Values, ExclusiveStartKey (references/language-adapters.md:56,111 ; assets/query-input.json:9-12) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | Request Parameters: "`ScanIndexForward` ... If `true` (default) ... ascending order; if `false` ... descending"; ReturnConsumedCapacity "Valid Values: `INDEXES / TOTAL / NONE`"; "`begins_with (` `sortKeyName`, `:sortkeyval` `)` - true if th | 2026-11-08 | VERIFIED |
|
|
288
|
+
| DP-E526 | Strongly consistent Query allowed on table, not on GSI (references/language-adapters.md:56 (ConsistentRead true on base table)) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | ConsistentRead: "Strongly consistent reads are not supported on global secondary indexes. If you query a global secondary index with `ConsistentRead` set to `true`, you will receive a `ValidationException`." | 2026-11-08 | VERIFIED |
|
|
289
|
+
| DP-E527 | Limit caps items evaluated (not matches), so returned matches <= Limit and cursor continues after the last evaluated item (references/language-adapters.md:32-35 ; assets/query-pages.mjs:43,47) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html | Limit: "The maximum number of items to evaluate (not necessarily the number of matching items)." | 2026-11-08 | VERIFIED |
|
|
290
|
+
| DP-E528 | JS: packages @aws-sdk/client-dynamodb (low-level) and @aws-sdk/lib-dynamodb (DynamoDBDocumentClient, native values); wrapNumbers option for lossless numbers (references/language-adapters.md:39-41,85-89) | https://github.com/aws/aws-sdk-js-v3/blob/main/lib/lib-dynamodb/README.md | README: "JavaScript objects passed in as parameters are marshalled into `AttributeValue` shapes required by Amazon DynamoDB." ; wrapNumbers: "returns numbers as NumberValue instances instead of native JavaScript numbers." (fetch | 2026-11-08 | VERIFIED |
|
|
291
|
+
| DP-E544 | Kotlin: aws.sdk.kotlin.services.dynamodb DynamoDbClient, `QueryRequest { tableName = ...; keyConditionExpression; expressionAttributeNames; expressionAttributeValues }`, `AttributeValue.S(..)`, suspend `client.query(request)` (references/language-adapters.md:122-148) | https://docs.aws.amazon.com/sdk-for-kotlin/latest/developer-guide/kotlin_dynamodb_code_examples.html | Query: `QueryRequest { tableName = tableNameVal keyConditionExpression = "$partitionAlias = :$partitionKeyName" expressionAttributeNames = attrNameAlias this.expressionAttributeValues = attrValues }` and `AttributeValue.S(parti | 2026-11-08 | VERIFIED |
|
|
292
|
+
| DP-E545 | Rust: `client.query().table_name().key_condition_expression().expression_attribute_names(k,v).expression_attribute_values(k, AttributeValue::S(..)).send().await`; `aws_sdk_dynamodb::types::AttributeValue` (references/language-adapters.md:160-181) | https://docs.aws.amazon.com/sdk-for-rust/latest/dg/rust_dynamodb_code_examples.html | Query: `.query().table_name(table_name).key_condition_expression("#yr = :yyyy").expression_attribute_names("#yr", "year").expression_attribute_values(":yyyy", AttributeValue::N(year.to_string())).send().await?` | 2026-11-08 | VERIFIED |
|
|
293
|
+
| DP-E546 | Rust builder methods `.consistent_read`, `.scan_index_forward`, `.limit`, `.set_exclusive_start_key`, `last_evaluated_key` (references/language-adapters.md:176-177) | https://docs.aws.amazon.com/sdk-for-rust/latest/dg/rust_dynamodb_code_examples.html | Query / Scan: Page shows `.limit(page_size)` only (Scan). The other method names are not shown on any fetched AWS page (docs.rs is third-party and was not used). | 2026-11-08 | UNVERIFIED |
|
|
294
|
+
| DP-E547 | Java 2.x `software.amazon.awssdk:dynamodb`, `QueryRequest.builder()...exclusiveStartKey`, `queryPaginator`, `legacy com.amazonaws.services.dynamodbv2`; PHP `Aws\DynamoDb\DynamoDbClient`, `Marshaler` (references/language-adapters.md:91-120,188-213) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ProgrammingWithJava.html | -: Not fetched in this pass. | 2026-11-08 | UNVERIFIED |
|
|
295
|
+
| DP-E530 | Partial throttled batch need not increment top-level ThrottledRequests (commands/performance-test.md:57-58) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | ThrottledRequests: "In a batch request (`BatchGetItem` or `BatchWriteItem`), `ThrottledRequests` is incremented only if *every* request in the batch is throttled." | 2026-11-08 | VERIFIED |
|
|
296
|
+
| DP-E531 | Vector request-byte metrics are not Query RCU/WCU; request returned capacity (commands/performance-test.md:60-63) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/VectorSearchMonitoring.html | Monitoring vector index capacity: "Vector index operations are metered in two units, separate from the read and write capacity units used by the base table" ; "set the `ReturnConsumedCapacity` parameter to `INDEXES` or `TOTAL` in your `SearchVectors` req | 2026-11-08 | VERIFIED |
|
|
297
|
+
| DP-E532 | SuccessfulRequestLatency is service-internal; client SLO measured separately (commands/performance-test.md:48-50) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TroubleshootingLatency.html | Troubleshooting latency: "The `SuccessfulRequestLatency` metric only measures latency which is internal to the DynamoDB service — client side activity and network trip times are not included." | 2026-11-08 | VERIFIED |
|
|
298
|
+
| DP-E533 | SDK retries can multiply service calls (commands/performance-test.md:36) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | SystemErrors: "most AWS SDKs automatically perform a configurable number of retries." | 2026-11-08 | VERIFIED |
|
|
299
|
+
| DP-E534 | `aws sts get-caller-identity` returns Account and Arn (commands/audit/live.md:29-36) | https://docs.aws.amazon.com/cli/latest/reference/sts/get-caller-identity.html | Output: "Account -> (string) The Amazon Web Services account ID number of the account that owns or contains the calling entity." / "Arn -> (string) The Amazon Web Services ARN associated with the calling entity." | 2026-11-08 | VERIFIED |
|
|
300
|
+
| DP-E535 | CLI global flags --no-cli-pager, --no-cli-auto-prompt, --output json, --profile, --region (commands/audit/live.md:28) | https://docs.aws.amazon.com/cli/latest/reference/sts/get-caller-identity.html | Global Options: "`--no-cli-auto-prompt` (boolean) Disable automatically prompt for CLI input parameters." | 2026-11-08 | VERIFIED |
|
|
301
|
+
| DP-E536 | `aws dynamodb describe-table --table-name` (commands/audit/live.md:37,63-64) | https://docs.aws.amazon.com/cli/latest/reference/dynamodb/describe-table.html | Synopsis / Options: "`--table-name` (string) [required] The name of the table to describe. You can also provide the Amazon Resource Name (ARN) of the table in this parameter." | 2026-11-08 | VERIFIED |
|
|
302
|
+
| DP-E537 | SearchVectors params: TableName, IndexName, TopK, SearchVector (list of AttributeValue), SearchConditionExpression, ExpressionAttributeNames/Values (assets/embedding-flow.py:83-89) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_SearchVectors.html | Request Parameters: "`IndexName` ... The name of the vector index to search. The index must be in the `ACTIVE` state." ; "`SearchConditionExpression` A condition expression used to filter the vector search results." | 2026-11-08 | VERIFIED |
|
|
303
|
+
| DP-E538 | TopK must be 1..100 (assets/embedding-flow.py:81-82) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_SearchVectors.html | TopK: "Valid values range from 1 to 100, inclusive." | 2026-11-08 | VERIFIED |
|
|
304
|
+
| DP-E539 | Search vector 1..4096 dims, must equal index dims, float32 elements in DynamoDB list format (assets/embedding-flow.py:25-27) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_SearchVectors.html | SearchVector: "Each element is a 32-bit IEEE-754 floating point number, provided in DynamoDB list format." ; "Array Members: Minimum number of 1 item. Maximum number of 4096 items." ; "The number of dimensions must match the number of | 2026-11-08 | VERIFIED |
|
|
305
|
+
| DP-E540 | Filter `#tenant = :tenant AND #status = :status` on search schema attributes (assets/embedding-flow.py:86-89) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_SearchVectors.html | SearchConditionExpression: "The `HASH` and `INLINE_FILTER` attributes support only the equality operator (`=`). You can reference only top-level attributes from the search schema." (combining two equalities with AND is not explicitly stated) | 2026-11-08 | VERIFIED |
|
|
306
|
+
| DP-E541 | COSINE distance function exists; Titan V2 model id amazon.titan-embed-text-v2:0 (assets/embedding-flow.py:3,10-11) | https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_SearchVectors.html | Description ; Example code: "`COSINE` - Returns the items with the *k smallest* scores." ; `model_id = "amazon.titan-embed-text-v2:0"` | 2026-11-08 | VERIFIED |
|
|
307
|
+
| DP-E542 | Titan V2 request body inputText, dimensions (1024), normalize, embeddingTypes ["float"]; response `embedding` (assets/embedding-flow.py:51-56) | https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-titan-embed-text.html | Request and response (V2): "dimensions – (optional) ... The following values are accepted: 1024 (default), 512, 256." ; "embedding – An array that represents the embedding vector of the input you provided. This will always be type `float`." ; "emb | 2026-11-08 | VERIFIED |
|
|
308
|
+
| DP-E543 | boto3 bedrock-runtime `invoke_model(modelId, contentType, accept, body)`; response["body"].read() (assets/embedding-flow.py:51-52) | https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-titan-embed-text.html | Example code: `response = bedrock.invoke_model(body=body, modelId=model_id, accept=accept, contentType=content_type)` and `json.loads(response.get('body').read())` | 2026-11-08 | VERIFIED |
|
|
309
|
+
| DP-E601 | On-demand backup copies the entire table each time; no limit on number of on-demand backups | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/CreateBackup.html | Backups: "Each time you create an on-demand backup, the entire table data is backed up. There is no limit to the number of on-demand backups that can be taken." | 2026-11-08 | VERIFIED |
|
|
310
|
+
| DP-E602 | Backups and restores consume no provisioned throughput on the table | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/CreateBackup.html | Backups: "All backups in DynamoDB work without consuming any provisioned throughput on the table." | 2026-11-08 | VERIFIED |
|
|
311
|
+
| DP-E603 | Restore can change GSIs, LSIs, billing mode, provisioned capacity and encryption settings; cross-Region restore to a different Region is supported | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/CreateBackup.html | Restores: "You can also restore your DynamoDB table data across AWS Regions such that the restored table is created in a different Region from where the backup resides." | 2026-11-08 | VERIFIED |
|
|
312
|
+
| DP-E604 | A restore never overwrites an existing table; it only restores to a new table | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/CreateBackup.html | Restores: "You can only restore the entire table data to a new table from a backup." | 2026-11-08 | VERIFIED |
|
|
313
|
+
| DP-E605 | AWS Backup can schedule and expire DynamoDB backups via backup plans | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/CreateBackup.html | Backups: "If you don't want to create scheduling scripts and cleanup jobs, you can use AWS Backup to create backup plans with schedules and retention policies for your DynamoDB tables." | 2026-11-08 | VERIFIED |
|
|
314
|
+
| DP-E606 | Tagging and ABAC are not supported for DynamoDB-native backups; use AWS Backup for ABAC; tags are not preserved on restored tables | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Backup-and-Restore.html | Backup and restore for DynamoDB: "Tagging and attribute-based access control (ABAC) aren't supported for DynamoDB backups." | 2026-11-08 | VERIFIED |
|
|
315
|
+
| DP-E607 | All DynamoDB backups are automatically encrypted | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Backup-and-Restore.html | Backup and restore for DynamoDB: "All backups are automatically encrypted, cataloged, and easily discoverable." | 2026-11-08 | VERIFIED |
|
|
316
|
+
| DP-E608 | DR guidance: PITR is continuous protection with RPO of seconds and RTO of minutes, in a single Region only | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamodbDisasterRecoveryStrategy.html | Choosing your disaster recovery strategy: "Continuous backups retained for up to 35 days, enabling PITR within seconds of any moment in the configured backup window" | 2026-11-08 | VERIFIED |
|
|
317
|
+
| DP-E609 | Global tables SLA is 99.999% availability versus 99.99% for single-Region tables | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Availability: "Global tables offer a 99.999% availability Service Level Agreement (SLA), compared to 99.99% for single-Region tables." | 2026-11-08 | VERIFIED |
|
|
318
|
+
| DP-E610 | MREC RPO equals replication delay between replicas, usually a few seconds | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Consistency modes: "MREC global tables have a Recovery Point Objective (RPO) equal to the replication delay between replicas, usually a few seconds depending on the replica Regions." | 2026-11-08 | VERIFIED |
|
|
319
|
+
| DP-E611 | MRSC supports an RPO of zero | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Consistency modes: "MRSC global tables support a Recovery Point Objective (RPO) of zero." | 2026-11-08 | VERIFIED |
|
|
320
|
+
| DP-E612 | Global tables failover is application-driven: shift traffic to another replica table | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html | Availability: "If a workload in a single AWS Region becomes impaired, you can shift application traffic to a different Region and perform reads and writes to a different replica table in the same global table." | 2026-11-08 | VERIFIED |
|
|
321
|
+
| DP-E613 | On-demand mode bills read request units and write request units | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html | Read request units and write request units: "DynamoDB charges you for the reads and writes that your application performs on your tables in terms of read request units and write request units." | 2026-11-08 | VERIFIED |
|
|
322
|
+
| DP-E614 | Provisioned mode bills hourly provisioned read and write capacity, not consumption | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/provisioned-capacity-mode.html | Provisioned capacity mode: "You'll be charged based on the hourly read and write capacity you have provisioned, not how much of that provisioned capacity you actually consumed." | 2026-11-08 | VERIFIED |
|
|
323
|
+
| DP-E615 | Storage billed on raw item bytes plus per-item overhead that depends on enabled features | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-understanding-billing.html | Storage: "DynamoDB measures the size of your billable data by adding the raw byte size of your data plus a per-item storage overhead that depends on the features you have enabled." | 2026-11-08 | VERIFIED |
|
|
324
|
+
| DP-E616 | Usage types differ by table class (Standard or Standard-IA) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-understanding-billing.html | Throughput Capacity: "The usage type depends on your table class (Standard or Standard-Infrequent Access)." | 2026-11-08 | VERIFIED |
|
|
325
|
+
| DP-E617 | PITR is billed on table size for as long as PITR is enabled | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Backup-and-Restore.html | Backup and restore for DynamoDB: "You get charged based on the size of your DynamoDB table for the duration you have PITR enabled on the table." | 2026-11-08 | VERIFIED |
|
|
326
|
+
| DP-E618 | On-demand backups are billed on size and duration of the backups | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Backup-and-Restore.html | Backup and restore for DynamoDB: "You're charged based on the size and duration of your backups." | 2026-11-08 | VERIFIED |
|
|
327
|
+
| DP-E619 | Restore billed on total GB restored including table data and indexes (usage type RestoreDataSize-Bytes) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-understanding-billing.html | Backup and Restore: "The total size of data restored (including table data, local secondary indexes and global secondary indexes) measured in GB from DynamoDB backups." | 2026-11-08 | VERIFIED |
|
|
328
|
+
| DP-E620 | Global table writes billed as replicated write units per replica; GSI updates billed with standard write units | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/global-tables-billing.html | How it works: "Replicated Write Request Units (rWRUs) for on-demand capacity mode, where one rWRU per replica table is charged for each write up to 1KB" | 2026-11-08 | VERIFIED |
|
|
329
|
+
| DP-E621 | No cross-Region data transfer fee for global table replication; MRSC witness incurs no replicated write, storage or transfer costs | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/global-tables-billing.html | How it works: "DynamoDB does not charge cross-Region data transfer fees for replicating data between the Regions of a global table." | 2026-11-08 | VERIFIED |
|
|
330
|
+
| DP-E622 | DynamoDB Streams reads are billed in read request units (each GetRecords call is one streams read request) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-understanding-billing.html | Streams: "DynamoDB Streams charges for reading data in read request units." | 2026-11-08 | VERIFIED |
|
|
331
|
+
| DP-E623 | GetRecords calls from Lambda triggers and from global tables replication are not charged | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-understanding-billing.html | Streams: "You are not charged for GetRecords API calls invoked by AWS Lambda as part of DynamoDB triggers or by DynamoDB global tables as part of replication." | 2026-11-08 | VERIFIED |
|
|
332
|
+
| DP-E624 | No charge for inbound transfer or for same-Region transfer to other AWS services; cross-Region transfer charged on both sides | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-understanding-billing.html | Data Transfer: "DynamoDB does not charge for inbound data transfer, and it does not charge for data transferred between DynamoDB and other AWS services within the same AWS Region" | 2026-11-08 | VERIFIED |
|
|
333
|
+
| DP-E625 | Contributor Insights is billed under CloudWatch (events processed and rules) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-understanding-billing.html | CloudWatch Contributor Insights: "CloudWatch Contributor Insights for DynamoDB is a diagnostic tool for identifying the most frequently accessed and throttled keys in your DynamoDB table." | 2026-11-08 | VERIFIED |
|
|
334
|
+
| DP-E626 | Reserved capacity is a upfront fee plus commitment for provisioned RCU/WCU | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-understanding-billing.html | Throughput Capacity: "With reserved capacity, you pay a one-time upfront fee and commit to a minimum provisioned usage level over a period of time." | 2026-11-08 | VERIFIED |
|
|
335
|
+
| DP-E627 | Each partition is designed for a maximum of 3,000 read units and 1,000 write units per second | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html | Best practices for designing and using partition keys: "Every partition in a DynamoDB table is designed to deliver a maximum capacity of 3,000 read units per second and 1,000 write units per second." | 2026-11-08 | VERIFIED |
|
|
336
|
+
| DP-E628 | Adaptive capacity applies to both on-demand and provisioned capacity | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html | Best practices for designing and using partition keys: "Adaptive capacity applies to on-demand mode and provisioned capacity." | 2026-11-08 | VERIFIED |
|
|
337
|
+
| DP-E629 | Throttling has four causes: key range (both modes), provisioned throughput, account quotas, on-demand maximum throughput | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TroubleshootingThrottling.html | Troubleshooting throttling: "Consumption directed at specific partitions exceeds the internal partition-level throughput limits." | 2026-11-08 | VERIFIED |
|
|
338
|
+
| DP-E630 | On-demand tables instantly accommodate up to double the previous peak | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html | Initial throughput and scaling properties: "On-demand capacity mode instantly accommodates up to double the previous peak traffic on a table." | 2026-11-08 | VERIFIED |
|
|
339
|
+
| DP-E631 | Throttling can occur if traffic exceeds double the previous peak within 30 minutes; pre-warm or space growth | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html | Initial throughput and scaling properties: "However, throttling can occur if you exceed double your previous peak within 30 minutes." | 2026-11-08 | VERIFIED |
|
|
340
|
+
| DP-E632 | Throttle exceptions carry ThrottlingReason fields (ResourceType+OperationType+LimitType) and the resource ARN | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html | Error handling with DynamoDB: "The error includes a list of ThrottlingReason fields that provides specific context about why throttling occurred" | 2026-11-08 | VERIFIED |
|
|
341
|
+
| DP-E633 | Cause-specific throttle metrics exist, e.g. ReadKeyRangeThroughputThrottleEvents for partition limits | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TroubleshootingThrottling-cloudwatch.html | CloudWatch throttling metrics: "Number of read requests throttled due to partition limits." | 2026-11-08 | VERIFIED |
|
|
342
|
+
| DP-E634 | Optional per-table maximum throughput on on-demand tables; requests above it are throttled | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html | DynamoDB on-demand capacity mode: "Throughput requests that exceed the maximum table throughput are throttled." | 2026-11-08 | VERIFIED |
|
|
343
|
+
| DP-E635 | AWS SDKs automatically retry requests that receive ProvisionedThroughputExceededException | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html | Error handling with DynamoDB: "The AWS SDKs for DynamoDB automatically retry requests that receive this exception." | 2026-11-08 | VERIFIED |
|
|
344
|
+
| DP-E636 | New on-demand tables sustain up to 4,000 writes and 12,000 reads per second initially | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html | Initial throughput and scaling properties: "New on-demand tables will be able to sustain up to 4,000 writes per second and 12,000 reads per second." | 2026-11-08 | VERIFIED |
|
|
345
|
+
| DP-E637 | AWS managed policy AmazonDynamoDBFullAccess exists | https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonDynamoDBFullAccess.html | AmazonDynamoDBFullAccess: "Provides full access to Amazon DynamoDB via the AWS Management Console." | 2026-11-08 | VERIFIED |
|
|
346
|
+
| DP-E638 | AWS managed policy AmazonDynamoDBReadOnlyAccess exists | https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonDynamoDBReadOnlyAccess.html | AmazonDynamoDBReadOnlyAccess: "Provides read only access to Amazon DynamoDB via the AWS Management Console." | 2026-11-08 | VERIFIED |
|
|
347
|
+
| DP-E639 | Resource-based policies are supported for tables, indexes and streams | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/access-control-resource-based.html | Using resource-based policies for DynamoDB: "DynamoDB supports resource-based policies for tables, indexes, and streams." | 2026-11-08 | VERIFIED |
|
|
348
|
+
| DP-E640 | IAM Access Analyzer reports cross-account access in resource-based policies | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/access-control-resource-based.html | Using resource-based policies for DynamoDB: "IAM Access Analyzer reports cross-account access to external entities specified in resource-based policies." | 2026-11-08 | VERIFIED |
|
|
349
|
+
| DP-E641 | Block Public Access is automatically enforced on resource-based policy changes with no setting to enable | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/rbac-bpa-rbp.html | Blocking public access with resource-based policies: "BPA is automatically enforced during these operations; there is no separate setting or configuration to enable it." | 2026-11-08 | VERIFIED |
|
|
350
|
+
| DP-E642 | Tags are supported on DynamoDB resources (tables) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html | Adding tags and labels to resources in DynamoDB: "You can label Amazon DynamoDB resources using tags." | 2026-11-08 | VERIFIED |
|
|
351
|
+
| DP-E643 | Tags support AWS bill breakdown / cost allocation reports | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html | Adding tags and labels to resources in DynamoDB: "Efficient tagging can provide cost insights by enabling you to create reports across services that carry a specific tag." | 2026-11-08 | VERIFIED |
|
|
352
|
+
| DP-E644 | Streams taggability: Tagging page says DynamoDB Streams usage cannot be tagged; Tagging DynamoDB Streams page (see DP-E318) says streams support tags added to existing streams and have their own ABAC. Treat Streams tagging as page-dependent | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html | Adding tags and labels to resources in DynamoDB: "Any local secondary indexes (LSI) and global secondary indexes (GSI) related to tagged tables are labeled with the same tags automatically. Currently, DynamoDB Streams usage cannot be tagged." | 2026-11-08 | CONFLICT |
|
|
353
|
+
| DP-E645 | Clients must support TLS 1.2 (TLS 1.3 recommended) with PFS cipher suites | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/inter-network-traffic-privacy.html | Securing DynamoDB connections using VPC endpoints and IAM policies: "Clients must support Transport Layer Security (TLS) 1.2." | 2026-11-08 | VERIFIED |
|
|
354
|
+
| DP-E646 | Gateway endpoint is a route-table gateway to DynamoDB over the AWS network; interface endpoints (PrivateLink) use private IPs | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/privatelink-interface-endpoints.html | Types of Amazon VPC endpoints for Amazon DynamoDB: "A gateway endpoint is a gateway that you specify in your route table to access DynamoDB from your Amazon VPC over the AWS network." | 2026-11-08 | VERIFIED |
|
|
355
|
+
| DP-E647 | Interface endpoints let VPC applications reach DynamoDB without public IP addresses | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/privatelink-interface-endpoints.html | AWS PrivateLink for DynamoDB: "Applications in your VPC do not need public IP addresses to communicate with DynamoDB using VPC interface endpoints for DynamoDB operations." | 2026-11-08 | VERIFIED |
|
|
356
|
+
| DP-E648 | Gateway endpoints are not billed (interface endpoints are billed) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/privatelink-interface-endpoints.html | Using gateway endpoints and interface endpoints together in the same Amazon VPC to access DynamoDB: "allow in-Amazon VPC applications to continue accessing DynamoDB through the gateway endpoint, which is not billed." | 2026-11-08 | VERIFIED |
|
|
357
|
+
| DP-E649 | PrivateLink does not support TLS 1.1 or private/hybrid DNS; use endpoint-specific URL, do not override DynamoDB DNS names with private hosted zones | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/privatelink-interface-endpoints.html | Considerations when using AWS PrivateLink for Amazon DynamoDB: "configure your clients to use the Amazon VPC endpoint URL directly" | 2026-11-08 | VERIFIED |
|
|
358
|
+
| DP-E650 | Each PrivateLink endpoint supports up to 50,000 requests per second | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/privatelink-interface-endpoints.html | Considerations when using AWS PrivateLink for Amazon DynamoDB: "You can submit up to 50,000 requests per second for each AWS PrivateLink endpoint that you enable." | 2026-11-08 | VERIFIED |
|
|
359
|
+
| DP-E651 | An endpoint policy on the VPC endpoint controls access to DynamoDB (principal, actions, resources) | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/privatelink-interface-endpoints.html | Creating an Amazon VPC endpoint policy for DynamoDB: "You can attach an endpoint policy to your Amazon VPC endpoint that controls access to DynamoDB." | 2026-11-08 | VERIFIED |
|
|
360
|
+
| DP-E652 | PrivateLink also supported for DynamoDB Streams endpoints | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/privatelink-interface-endpoints.html | AWS PrivateLink for DynamoDB: "AWS PrivateLink is also supported for Amazon DynamoDB Streams endpoints." | 2026-11-08 | VERIFIED |
|
|
361
|
+
| DP-E653 | For requests from a VPC endpoint, both IAM and VPC endpoint policies must authorize DescribeEndpoints | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/inter-network-traffic-privacy.html | Required policy for endpoints: "For requests from a VPC endpoint, both the IAM and Virtual Private Cloud (VPC) endpoint policies must authorize the DescribeEndpoints API call" | 2026-11-08 | VERIFIED |
|
|
362
|
+
| DP-E654 | Page says Amazon VPC endpoints are not accessible through Site-to-Site VPN or Direct Connect, while PrivateLink page says interface endpoints are accessible from on premises over VPN and Direct Connect; the first note does not state which endpoint type it means | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/inter-network-traffic-privacy.html | Traffic between AWS resources in the same Region: "Amazon VPC endpoints are not accessible through AWS Site-to-Site VPN or Direct Connect." | 2026-11-08 | CONFLICT |
|
|
363
|
+
| DP-E655 | CloudTrail captures all DynamoDB API calls, including console, SDK, PartiQL and classic API | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/logging-using-cloudtrail.html | Logging DynamoDB operations by using AWS CloudTrail: "CloudTrail captures all API calls for DynamoDB as events." | 2026-11-08 | VERIFIED |
|
|
364
|
+
| DP-E656 | Control plane actions (table, backup, global table, tag, TTL, DAX, Streams describe/list) are logged by default | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/logging-using-cloudtrail.html | Control plane events in CloudTrail: "The following API actions are logged by default as events in CloudTrail files:" | 2026-11-08 | VERIFIED |
|
|
365
|
+
| DP-E657 | Data plane (item-level) API logging must be explicitly enabled as CloudTrail data events | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/logging-using-cloudtrail.html | DynamoDB data plane events in CloudTrail: "To enable logging of the following API actions in CloudTrail files, you must enable logging of data plane API activity in CloudTrail." | 2026-11-08 | VERIFIED |
|
|
366
|
+
| DP-E658 | Data events can be filtered by resource type (AWS::DynamoDB::Table, AWS::DynamoDB::Stream) to control logging and cost | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/logging-using-cloudtrail.html | DynamoDB data plane events in CloudTrail: "Data plane events can be filtered by resource type, for granular control over which DynamoDB API calls you want to selectively log and pay for in CloudTrail." | 2026-11-08 | VERIFIED |
|
|
367
|
+
| DP-E659 | TTL data plane deletions are not logged by CloudTrail | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/logging-using-cloudtrail.html | DynamoDB data plane events in CloudTrail: "DynamoDB Time to Live data plane actions are not logged by CloudTrail" | 2026-11-08 | VERIFIED |
|
|
368
|
+
| DP-E660 | GetRecords data events include internal global tables replication calls and are billed by CloudTrail | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/logging-using-cloudtrail.html | DynamoDB data plane events in CloudTrail: "Although you are not charged by DynamoDB for these GetRecords calls, you are charged by CloudTrail for the data event logs." | 2026-11-08 | VERIFIED |
|
|
369
|
+
| DP-E661 | Without a trail, recent events remain viewable in CloudTrail Event history | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/logging-using-cloudtrail.html | Logging DynamoDB operations by using AWS CloudTrail: "If you don't configure a trail, you can still view the most recent events in the CloudTrail console in Event history." | 2026-11-08 | VERIFIED |
|
|
370
|
+
| DP-E662 | Backup and restore API actions are recorded in CloudTrail | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/CreateBackup.html | Restores: "All backup and restore console and API actions are captured and recorded in AWS CloudTrail for logging, continuous monitoring, and auditing." | 2026-11-08 | VERIFIED |
|
|
371
|
+
| DP-E663 | Metrics are sent to CloudWatch; consumed provisioned throughput is emitted per one-minute period | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | DynamoDB Metrics and dimensions: "DynamoDB outputs consumed provisioned throughput for one-minute periods." | 2026-11-08 | VERIFIED |
|
|
372
|
+
| DP-E664 | DynamoDB CloudWatch metrics live in the AWS/DynamoDB namespace | https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/alarms-and-missing-data.html | Configuring how CloudWatch alarms treat missing data: "Alarms that evaluate metrics in the AWS/DynamoDB namespace default to ignore missing data." | 2026-11-08 | VERIFIED |
|
|
373
|
+
| DP-E665 | Usage metrics integrate with Service Quotas and CloudWatch alarms can alert when usage approaches a threshold | https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html | Usage metrics: "configuring alarms that alert you when usage approaches a threshold." | 2026-11-08 | VERIFIED |
|