Integrations · NoSQL · Coming next
Amazon DocumentDB: coming next connector
Amazon DocumentDB (instance-based clusters) through the MongoDB connector, with its own compatibility record: collection discovery, field shapes inferred from a bounded sample inside your network, _id or unique-index-backed business keys, document counts, aggregate profiles and bounded streaming reads. MongoDB compatibility is never assumed: DocumentDB is detected and tested separately.
Coming next NoSQL
Active implementation; not yet available for production use.
Amazon DocumentDB has no foreign keys. DataNivra cannot discover relationships from Amazon DocumentDB: 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.
Not available yet. Active implementation; not yet available for production use. There is no DataNivra connector for it today.
What you can do today
Export collections with mongoexport to JSON inside your VPC, convert them to Parquet and read them with the shipped Local files or object-store connectors.
Whatever route you choose, the export and every row-level step stay inside your network. You can evaluate the whole workflow now with the synthetic demo.
Known limitations
- Requires agent 0.4.3 or later: earlier agents treat DocumentDB as MongoDB and refuse it when its proof cannot be completed (fail closed).
- DocumentDB clusters are reachable only inside their VPC: the agent must run in that VPC, a peered network or behind a tunnel you operate.
- Fields are inferred from a bounded $sample per collection; where a cluster does not support $sample, from the first sample_size documents in natural order.
- SCRAM password authentication only (no IAM authentication).
- DocumentDB declares no relationships: they come from industry packs or explicit mappings.
- Instance-based clusters only; DocumentDB Elastic Clusters are not tested.
Capability matrix
Amazon DocumentDB does not ship yet, so no capability is verified. The column shows what the design plans; plans are not commitments.
| Capability | Design intent |
|---|---|
| Discovery | Planned |
| Classification | Planned |
| Profiling | Planned |
| Masking | Planned |
| Deterministic masking | Planned |
| Entity-aware subsetting | Not planned yet |
| Relationship preservation | Not planned yet |
| Synthetic workflows | Not planned yet |
| Certification | Planned |
| Provisioning | Not planned yet |
| CI/CD | Not planned yet |
| Evidence generation | Planned |
How the connector is designed to prove read-only access
Proven before reading from connectionStatus: where DocumentDB returns the user's expanded privileges, every action must be a read action (as for MongoDB); otherwise every role must be the built-in read or readAnyDatabase role, or a custom role whose privileges (rolesInfo) hold only read actions. readWrite, administration, monitoring and backup roles refuse the source, and so does any role whose privileges cannot be read.
Served by the MongoDB connector, which detects DocumentDB from the cluster endpoint name and the server's buildInfo (set "flavor": "documentdb" to refuse any other server); evidence is recorded separately. TLS is verified against the Amazon RDS CA bundle shipped with the connector (certificate and host name) unless tls_ca_file is set.
Planned authentication: SCRAM username and password over TLS (secret reference).
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.
Request this connector
We prioritise connectors by demand, engineering effort and strategic fit. Telling us that Amazon DocumentDB matters to you is counted; it does not commit a delivery date.
Need something specific from the Amazon DocumentDB connector? Request a feature (please describe it without real data).
All integrations · NoSQL test data management · Guides · Start free