Integrations · NoSQL · Available now
Amazon DynamoDB test data, inside your network
Amazon DynamoDB connector (boto3): table discovery, partition and sort keys, attribute shapes inferred from a bounded scan inside your network, and eventually consistent, paginated scans under a read-capacity budget with nested attributes carried as JSON text.
Available now NoSQL
Shipped in the standard agent and backed by recorded conformance evidence.
Amazon DynamoDB has no foreign keys. DataNivra cannot discover relationships from Amazon DynamoDB: they come from an industry pack’s relationship mappings or relationships you declare. Without declared relationships, subsets do not follow relationships and the orphan check cannot cover them.
The console warns before a build that has none, and the certificate records RELATIONSHIPS_NOT_DECLARED for that source instead of reporting zero orphans as a check.
What works today
Amazon DynamoDB connector (boto3): table discovery, partition and sort keys, attribute shapes inferred from a bounded scan inside your network, and eventually consistent, paginated scans under a read-capacity budget with nested attributes carried as JSON text.
IAM access key as secret references, or the agent host's default credential chain. Scans use Limit, ConsistentRead=false and projections; consumed read capacity is metered and throttled requests back off.
Authentication: IAM access key (secret reference); default AWS credential chain (instance profile, workload identity).
Known limitations
- Requires agent 0.4.0 or later (its driver, boto3, ships in the standard agent image).
- Run against one real AWS account (us-east-1, on-demand tables, IAM-user reader proven read-only by policy simulation) and DynamoDB Local; provisioned-capacity tables, global tables, resource-policy grants and assumed-role principals are untested.
- Attributes are inferred from a bounded scan sample; a later item whose attribute type differs stops the read with FIELD_TYPE_DRIFT.
- Exact counts scan the table under the read budget; discovery reports DynamoDB's ItemCount, which is refreshed about every six hours.
- DynamoDB declares no relationships: they come from industry packs or explicit mappings.
Capability matrix
Each capability is tracked separately and shown at the level the recorded conformance evidence supports. A connector that only discovers metadata is never presented as equivalent to one that runs the whole workflow.
| Capability | Level |
|---|---|
| Discovery | Supported |
| Classification | Supported |
| Profiling | Supported |
| Masking | Supported |
| Deterministic masking | Supported |
| Entity-aware subsetting | Supported |
| Relationship preservation | Supported |
| Synthetic workflows | Supported |
| Certification | Supported |
| Provisioning | Supported |
| CI/CD | Supported |
| Evidence generation | Supported |
Read-only proof
Verified where the principal may call iam:SimulatePrincipalPolicy: PutItem, UpdateItem, DeleteItem, BatchWriteItem, PartiQL writes and table changes are simulated on every exposed table (with its resource policy) and any allowed write refuses the source. Otherwise the operator must attest read-only access, and the source is refused without it.
Conformance evidence
DataNivra runs every connector through a common conformance kit on synthetic data: no write statements, proven read-only access, secret redaction, schema and relationship discovery, bounded streaming, cancellation, clear reason codes, egress canaries and no raw values in logs, then the discover, mask, subset, certify and provision workflow. The published status is computed from those results.
| Engine or service | Version | Environment | Driver | Authentication | Verified on |
|---|---|---|---|---|---|
| Amazon DynamoDB | service | managed-service | boto3 1.43.106 | IAM access key (policy simulation) | 2026-10-12 |
Connector version 0.1.0, last verified 2026-10-12.
What crosses the boundary
Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:
- Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
- Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
- Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
- Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.
Never sent:
- Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
- Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
- Free text copied from your data, or exception messages that contain values.
See the customer-resident architecture and how to verify these claims yourself.
Setup outline
- Use agent 0.4.0 or later: the standard agent image includes the DynamoDB driver (boto3).
- Create an IAM role or user allowed only DescribeTable, Scan and GetResourcePolicy on the tables to read, ListTables, and iam:SimulatePrincipalPolicy on itself, so the agent can prove from IAM that the credential cannot write. Without that proof the source is refused unless you attest read-only access.
- Store the connection document with access keys as secret references, or omit them so the agent uses its host credential chain (instance profile or workload identity). Scans are eventually consistent and metered against a read-capacity budget you set.
- In the console, register the source with the secret reference of that document (for example vault://tdm/source-connection) and the agent that can reach it, then run discovery.
Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):
{
"kind": "AMAZON_DYNAMODB",
"region": "eu-west-1",
"tables": ["members", "claims"],
"access_key_id_ref": "vault://tdm/dynamodb-reader#access_key_id",
"secret_access_key_ref": "vault://tdm/dynamodb-reader#secret_access_key"
}Next: install the agent, then follow the getting started guide.
All integrations · NoSQL test data management · Guides · Start free