DocumentDB Connector

Route device telemetry to Amazon DocumentDB (MongoDB-compatible) for flexible document storage with rich query capabilities. Store complex nested telemetry structures and perform aggregation pipelines for advanced analytics.

What is DocumentDB

Amazon DocumentDB is a fully managed document database service that supports MongoDB workloads. It provides the scalability and durability of AWS with the MongoDB API compatibility that developers already know.

Key Features:

MongoDB Compatibility: Use existing MongoDB drivers, tools, and query syntax without modifications.

Flexible Schema: Store heterogeneous telemetry from different device types in the same collection.

Aggregation Pipelines: Perform complex data transformations and analytics at the database level.

Secondary Indexes: Create indexes on any field for fast queries across device ID, timestamp, or sensor values.

Auto-scaling Storage: Storage automatically grows in 10GB increments up to 128TB.

How it Works

When the DocumentDB connector is enabled, /IOTCONNECT™ inserts device telemetry as JSON documents into your DocumentDB cluster:

Device sends telemetry → /IOTCONNECT™ receives and validates the payload.

Document created → Telemetry is formatted as a JSON document with full device context.

Inserted to collection → Document is written to the configured DocumentDB collection.

Queryable immediately → Use MongoDB queries, aggregation, and indexes for real-time analytics.

User Manual

Step 1: Navigate to Connector Settings

Go to Settings > Configuration > Live Data Streaming in the /IOTCONNECT™ portal.

Step 2: Enable DocumentDB

Find the DocumentDB connector card and toggle the switch to ON (green).

Step 3: Select Data Types

Choose which data to route: Telemetry, Faulty, Diagnostics, Command History.

Step 4: Run CloudFormation Stack

Click the CloudFormation link. This creates:

A DocumentDB cluster with replica instances

VPC, subnets, and security groups for network isolation

IAM cross-account role for secure access

Database and collection with TTL indexes

Step 5: Confirm Account ID

Account ID auto-populates after stack completion.

Step 6: Save

Click Save. Documents begin flowing to your DocumentDB cluster.

Use Cases

Complex Telemetry: Store deeply nested JSON from devices with variable sensor configurations.

Real-time Analytics: Run aggregation pipelines for average, min, max, and percentile calculations on telemetry.

Multi-tenant Data: Use collection-per-tenant or filtered queries for isolated multi-tenant analytics.

Geospatial Queries: Index device location data and perform geospatial queries for fleet tracking.

Application Backend: Serve as the primary database for custom IoT applications using MongoDB drivers.

ⓘ NOTE

DocumentDB runs inside a VPC for network security. Use TTL indexes to automatically expire old documents and manage storage costs. Backup and point-in-time recovery are enabled by default.