AWS SQS

Connect Webhook Relay to Amazon SQS to poll messages from queues (input) or send webhook data as SQS messages (output).

Prerequisites

• An AWS service connection with credentials that have SQS permissions
• An SQS queue in your AWS account

IAM Permissions

For SQS Input (poll messages):

• sqs:ReceiveMessage
• sqs:DeleteMessage
• sqs:GetQueueAttributes

For SQS Output (send messages):

• sqs:SendMessage

SQS Input — Poll Messages from a Queue

SQS inputs use long-polling (20-second wait, up to 10 messages per poll) to continuously receive messages from your queue. Messages are deleted from the queue after successful relay into your bucket.

Configuration

Once added, you can test it by using "Send and receive messages" button:

SQS Output — Send Webhooks to a Queue

SQS outputs forward incoming webhook data as messages to your SQS queue. Every webhook that arrives in the bucket is sent as an SQS message.

Configuration

Example: Bridge GCP Pub/Sub to AWS SQS

Route messages from a GCP Pub/Sub subscription into an AWS SQS queue. This is ideal for cross-cloud event processing where your consumers read from SQS:

1. Create a GCP service connection with Pub/Sub subscriber permissions
2. Create an AWS service connection with SQS send permissions
3. Create a bucket in Webhook Relay
4. Add a GCP Pub/Sub input on the bucket
5. Add an AWS SQS output on the bucket

Messages published to the Pub/Sub topic are automatically delivered to your SQS queue.

Transform Between Formats

GCP Pub/Sub and AWS SQS use different message formats. Attach a Function to the bucket to reshape the payload. For example, convert a Pub/Sub message into a structured format for your SQS consumers:

const pubsubMessage = JSON.parse(r.body)

// Restructure for your SQS consumer
const sqsPayload = {
    source: "gcp-pubsub",
    topic: pubsubMessage.subscription,
    data: pubsubMessage.data,
    attributes: pubsubMessage.attributes,
    received_at: new Date().toISOString()
}

r.setBody(JSON.stringify(sqsPayload))

See the JSON encoding guide for more payload transformation examples.

Example: SQS to HTTPS Webhook Delivery

Poll messages from an SQS queue and forward them to any HTTPS endpoint — useful when you want to process SQS messages with a service that only accepts webhooks:

1. Create an AWS service connection
2. Create a bucket with an SQS input pointing to your queue
3. Add a public destination as an output

You can also forward to localhost for local development, letting you consume SQS messages on your machine without deploying to AWS.

Example: Fan-Out from SQS to Multiple Destinations

A single SQS input can feed multiple outputs on the same bucket. For example, forward SQS messages simultaneously to:

• A GCP Pub/Sub topic (cross-cloud replication)
• An S3 bucket (archival)
• An HTTPS API (real-time processing)

This lets you fan out messages without configuring multiple SQS consumers or SNS subscriptions.