Amazon SQS Tools

The Amazon SQS provider lets a workflow interact with Amazon Simple Queue Service (SQS): send messages onto a queue, receive (poll) messages from a queue, and list the queues in an AWS account. Use these tools to decouple workflow steps from downstream consumers, fan out work to a queue, or drain pending messages for processing. Requests are signed directly with AWS Signature Version 4 (SigV4) using your AWS access key credentials — no AWS SDK or proxy is required.

Overview

Operations

All three operations issue a signed POST to https://sqs.{awsRegion}.amazonaws.com/ using the AWS JSON protocol (the X-Amz-Target header selects the specific SQS action).

Configuration

sqs_send_message

Send a message to an Amazon SQS queue.

sqs_receive_message

Receive messages from an Amazon SQS queue.

sqs_list_queues

List Amazon SQS queues, optionally filtered by name prefix.

Outputs

sqs_send_message

• data (json) — SQS SendMessage result (e.g. MessageId, MD5OfMessageBody).

sqs_receive_message

• data (json) — SQS ReceiveMessage result (a Messages array; empty/absent when no messages are available).

sqs_list_queues

• data (json) — SQS ListQueues result (a QueueUrls array).

YAML Example

sqs_1:
  type: sqs
  name: "Amazon SQS"
  inputs:
    operation: "sqs_send_message"
    awsRegion: "us-east-1"
    awsAccessKeyId: "{{AWS_ACCESS_KEY_ID}}"
    awsSecretAccessKey: "{{AWS_SECRET_ACCESS_KEY}}"
    queueUrl: "https://sqs.us-east-1.amazonaws.com/123456789012/my-queue"
    messageBody: "Hello from Zelaxy"
  connections:
    outgoing:
      - target: next-block-id

To receive messages instead, set operation: "sqs_receive_message" with queueUrl (and optional maxMessages); to list queues, set operation: "sqs_list_queues" with an optional prefix. Reference the result downstream with {{sqs_1.data}} (for example, the message id after a send or the Messages array after a receive).

Tips

• Auth is AWS SigV4, not an API key or OAuth. You must supply awsRegion, awsAccessKeyId, and awsSecretAccessKey on every operation; each request is signed individually. Store the access key id and secret as secrets/environment variables (e.g. {{AWS_ACCESS_KEY_ID}}, {{AWS_SECRET_ACCESS_KEY}}) rather than inlining them.
• The awsRegion must match the region of your queueUrl — it is used to build both the endpoint host (https://sqs.{awsRegion}.amazonaws.com/) and the signing scope, so a mismatch will fail signature verification or hit the wrong queue.
• sqs_receive_message returns up to maxMessages (1-10, default 10) and may legitimately return no Messages when the queue is empty — handle the empty case downstream. Note this tool receives messages but does not delete them; messages will reappear after the queue's visibility timeout unless you delete them separately.