Skip to main content

AWS-SQS

📩 AWS SQS Integration

Summary (SEO Meta Description):
The AWS SQS Integration in WeHub connects workflows to Amazon Simple Queue Service (SQS).
It supports subscribing to queues as triggers and publishing or managing messages as processors, enabling event-driven and asynchronous workflows.


🔎 Overview

The AWS SQS Integration allows WeHub workflows to interact with Amazon SQS queues for message publishing, subscribing, and management.
It supports both Standard and FIFO queues, ensuring reliability, scalability, and flexibility for modern event-driven architectures.

Why use AWS SQS in WeHub?

  • Decouple microservices using queues
  • Scale event-driven workflows seamlessly
  • Ensure reliable message delivery with retries
  • Handle high-throughput or bursty workloads

📂 Available Actions

ActionCategoryDescription
SubscribeTriggerListen for new messages in an SQS queue and start workflows.
PublishProcessorSend messages to an SQS queue.
Delete MessageProcessorDelete messages after processing to prevent duplicates.
Purge QueueProcessorClear all messages from a queue.

💡 Example Use Cases

  • Healthcare → Queue HL7/FHIR events for downstream clinical systems.
  • Finance → Publish and consume transaction events for fraud detection.
  • IoT → Collect telemetry from devices asynchronously.
  • Operations → Buffer workload spikes with SQS queues.

❓ FAQ

Q: Does this integration support FIFO queues?
A: Yes. FIFO queues ensure strict ordering and exactly-once delivery.

Q: What IAM permissions are required?
A: The AWS connection must allow:

  • sqs:SendMessage
  • sqs:ReceiveMessage
  • sqs:DeleteMessage
  • sqs:PurgeQueue

Q: Can multiple workflows subscribe to the same SQS queue?
A: Yes, but configure carefully to avoid duplicate or out-of-order processing.


Keywords: AWS SQS Integration, WeHub SQS, Amazon Simple Queue Service, Workflow Queues, FIFO Queue, Event-Driven Workflows