AWS SQS
Use this node to enqueue messages in an AWS SQS queue (Standard or FIFO) — for example, buffering device telemetry for async processing by a Lambda consumer, or routing commands to device-specific FIFO queues to guarantee ordered delivery.
Configuration
Section titled “Configuration”- Queue type —
STANDARDorFIFO. For FIFO queues, message deduplication ID = TB message ID; message group ID = originator entity ID. - Queue URL pattern — required. Full SQS queue URL. Supports templatization.
- Delay seconds — delivery delay for Standard queues (0–900). Not applicable to FIFO queues.
- Message attributes — custom SQS message attributes. Both name and value support templatization.
- AWS Access Key ID / Secret Access Key / Region — required. IAM credentials with SQS send permissions.
Fixed timeouts: 10 s connection, 5 s request.
Outgoing message format
Section titled “Outgoing message format”On Success, adds to metadata: messageId, requestId, messageBodyMd5, messageAttributesMd5 (if attributes present), sequenceNumber (FIFO queues only).
On Failure, adds to metadata: error.
Message processing algorithm
Section titled “Message processing algorithm”- Resolve the queue URL pattern and message attribute templates from message data and metadata.
- Enqueue the message data as the SQS message body.
- On success: add response metadata fields; route via
Success. - On error: add
errorto metadata; route viaFailure.
Output connections
Section titled “Output connections”| Connection | Condition |
|---|---|
Success | Message enqueued. Metadata includes messageId, requestId, and MD5 hashes. |
Failure | Timeout, SQS error, invalid credentials, or unexpected error. |
Examples
Section titled “Examples”Example 1 — Standard queue with delay
Section titled “Example 1 — Standard queue with delay”{ "queueType": "STANDARD", "queueUrlPattern": "https://sqs.us-east-1.amazonaws.com/123456789012/telemetry-queue", "delaySeconds": 0, "messageAttributes": {}, "accessKeyId": "AKIAIOSFODNN7EXAMPLE", "secretAccessKey": "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY", "region": "us-east-1"}Routes via Success with messageId and requestId added to metadata.
JSON schema
Section titled “JSON schema”{ "$schema": "https://json-schema.org/draft/2020-12/schema", "title": "TbSqsNodeConfiguration", "type": "object", "required": ["queueType", "queueUrlPattern", "accessKeyId", "secretAccessKey", "region"], "additionalProperties": false, "properties": { "queueType": { "type": "string", "enum": ["STANDARD", "FIFO"] }, "queueUrlPattern": { "type": "string" }, "delaySeconds": { "type": "integer", "minimum": 0, "maximum": 900 }, "messageAttributes": { "type": "object", "additionalProperties": { "type": "string" } }, "accessKeyId": { "type": "string" }, "secretAccessKey": { "type": "string" }, "region": { "type": "string" } }}