SQS Connector

Queue device telemetry and events in Amazon SQS for reliable asynchronous processing. Guaranteed message delivery with dead-letter queues, batch operations, and configurable visibility timeout for consumer flexibility.

What is SQS

Amazon SQS (Simple Queue Service) is a fully managed message queuing service that decouples and scales microservices, distributed systems, and serverless applications. It eliminates the complexity of managing message middleware.

Key Features:

Guaranteed Delivery: Messages are stored redundantly and guaranteed to be delivered at least once.

Dead-letter Queues: Failed messages are moved to a DLQ for troubleshooting without blocking processing.

Batch Operations: Send, receive, and delete up to 10 messages at a time for throughput optimization.

FIFO Queues: Exactly-once processing with strict message ordering for sequential IoT operations.

Serverless Integration: Trigger Lambda functions directly from SQS messages for event-driven processing.

How it Works

When the SQS connector is enabled, /IOTCONNECT™ sends device data as messages to your SQS queue:

Device sends data → /IOTCONNECT™ receives and processes telemetry or events.

Message enqueued → Data is formatted as a JSON message and sent to your SQS queue.

Consumer polls → Your application or Lambda function polls the queue and processes messages.

Message deleted → After successful processing, the message is deleted from the queue.

If a consumer fails to process a message within the visibility timeout, it becomes available for retry. After max retries, it moves to the dead-letter queue.

Video Walkthrough: Amazon SQS Connector | Configuration

Watch the complete walkthrough video showing the end-to-end process of configuring the Amazon SQS connector and validating device data messages with the IoTConnect platform.

User Manual

Step 1: Navigate to Connector Settings

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

Step 2: Enable SQS

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

Step 3: Select Data Types

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

Step 4: Run CloudFormation Stack

Click the CloudFormation link. This creates:

An SQS queue with optimized configuration

A dead-letter queue for failed message handling

Queue policy for cross-account message sending

IAM role with SendMessage permission

Step 5: Confirm Account ID

Account ID auto-populates after stack completion.

Step 6: Save

Click Save. Messages begin flowing to your SQS queue.

Use Cases

Async Processing: Decouple high-volume telemetry from slow downstream processes (ETL, enrichment).

Load Leveling: Buffer bursts of device data during peak hours and process at a steady rate.

Microservice Communication: Feed IoT data to multiple downstream microservices reliably.

Retry Logic: Process device commands with guaranteed delivery and automatic retry on failure.

Batch Processing: Accumulate telemetry messages and process them in batches for efficiency.

ⓘ NOTE

SQS messages are retained for up to 14 days. Configure visibility timeout based on your consumer processing time. Use FIFO queues when message order matters for your IoT workflow.