3 of these connectors can be used today (available or in preview); the others are shown with their honest status. Statuses are derived from recorded conformance evidence.
Available now
MongoDB
Shipped in the standard agent and backed by recorded conformance evidence.
MongoDB connector (pymongo): 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 with nested documents carried as JSON text.
Available now — details about MongoDB
Available now
Azure Cosmos DB
Shipped in the standard agent and backed by recorded conformance evidence.
Azure Cosmos DB for NoSQL connector (azure-cosmos): container discovery, field shapes inferred from a bounded sample inside your network, partition-key-aware keys, RU-budgeted paged queries and nested items carried as JSON text.
Available now — details about Azure Cosmos DB
Available now
Amazon DynamoDB
Shipped in the standard agent and backed by recorded conformance evidence.
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 — details about Amazon DynamoDB
Coming next
Amazon DocumentDB
Active implementation; not yet available for production use.
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 — details about Amazon DocumentDB