Connectors – iotconnect

Connectors

/IOTCONNECT™ connectors enable seamless data routing from your IoT devices to external cloud services. Configure storage, databases, messaging queues, ML endpoints, and live streaming to extend your data pipeline beyond the platform.

What are Connectors

Connectors are pre-built integrations that route your device telemetry, events, and diagnostics from /IOTCONNECT™ to external cloud services in real time. Once enabled, data flows automatically without any custom code.

Why use Connectors:

Long-term Storage: /IOTCONNECT™ retains data for 3 months by default. Connectors let you archive telemetry permanently in your own storage.

Custom Analytics: Feed data to your own analytics tools, data lakes, or ML pipelines for advanced insights.

Real-time Streaming: Push live telemetry to dashboards, mobile apps, or third-party systems via WebSocket, SignalR, or MQTT.

Event-driven Architecture: Route device events to messaging queues for async processing and fan-out notifications.

Connectors

DynamoDB

Fast key-value NoSQL database with single-digit millisecond performance. Ideal for real-time device state tracking and time-series data.

S3 Bucket

Scalable object storage for telemetry archival. Supports JSON, CSV, Parquet with date partitioning for analytics.

SNS

Publish device events to topics for fan-out to email, SMS, HTTP, Lambda, and SQS. Supports message filtering.

SageMaker

Route telemetry to ML inference endpoints for real-time predictions, anomaly detection, and predictive maintenance.

DocumentDB

MongoDB-compatible document database for flexible JSON queries and complex nested telemetry structures.

SQS

Reliable message queuing for async processing. Guaranteed delivery with dead-letter queues and batch operations.

SignalR

Real-time web communication. Push live device data to browser dashboards without polling.

WebSocket

Direct WebSocket connections for real-time streaming to custom applications and mobile apps.

MQTT

Lightweight pub-sub messaging to stream telemetry to external MQTT brokers for third-party integrations.

Cosmos DB

Globally distributed multi-model database. Document, key-value, and graph workloads with geo-replication.

Blob Storage

Massively scalable object storage for telemetry archival, log files, and unstructured IoT data.

Service Bus

Enterprise messaging with queues and topics. Reliable delivery for mission-critical IoT event processing.

Event Hub

High-throughput event streaming. Millions of events per second with partitioned consumption for analytics.

Data Lake Gen 2

Hierarchical namespace storage optimized for big data analytics. Petabyte-scale with HDFS-compatible access.

Reporting Database

Dedicated SQL database for structured reporting and BI dashboards. Optimized for aggregated telemetry queries.

SignalR

Real-time web communication for Azure. Push live device data to browser dashboards without polling.

MQTT

Lightweight pub-sub messaging to stream telemetry to external MQTT brokers for third-party integrations.

How to Enable a Connector

All connectors are configured from Settings > Configuration > Live Data Streaming in the /IOTCONNECT™ portal:

Step 1: Toggle the connector switch to ON (green).

Step 2: Select data types to route: Telemetry, Faulty, Diagnostics, Command History.

Step 3: Click the setup link to auto-provision resources (CloudFormation for AWS, ARM template for Azure).

Step 4: Account ID / Subscription ID populates automatically after stack completes.

Step 5: Click Save. Data flows immediately to the configured service.

ⓘ NOTE

Connectors use cross-account IAM roles (AWS) or Service Principals (Azure) for secure access. Resources are auto-provisioned via CloudFormation or ARM templates. /IOTCONNECT™ stores data for 3 months by default — set up connectors for permanent storage beyond this retention period.

Connectors
What are Connectors
How to Enable a Connector