This connector enables integration with Amazon Simple Queue Service (SQS), AWS's fully managed message
queuing service. Send messages to SQS queues for decoupled, scalable application architectures.

Prerequisites

To use this connector, you need:

• An AWS account with SQS access
• An IAM role with SQS permissions
• Our AWS Account ID (see 'AWS Account ID' in the 'Setup Information' section below)
• External ID: Generated automatically during connection setup

Authentication Setups

This connector uses AWS IAM Role ARN authentication with an external ID for enhanced security.

Step 1: Create IAM Policy

In your AWS account, create a new IAM policy with the following permissions:

{
"Version": "2012-10-17",
"Statement": [
  {
    "Effect": "Allow",
    "Action": [
      "sqs:SendMessage",
      "sqs:GetQueueUrl",
      "sqs:GetQueueAttributes"
    ],
    "Resource": "arn:aws:sqs:*:*:*"
  }
]
}

For better security, replace "Resource": "arn:aws:sqs:*:*:*" with the specific queue ARN(s).

Step 2: Create IAM Role

1. In the AWS IAM console, create a new role
2. Select "Another AWS account" as the trusted entity
3. Enter the AWS Account ID shown in the 'Setup Information' section below as AWS Account ID.
4. Check "Require external ID" and enter the External ID shown in the 'Setup Information' section below
5. Attach the policy created in Step 1
6. Complete role creation and copy the Role ARN

Step 3: Configure Connection

1. Paste the Role ARN from your AWS role
2. Select the AWS Region where your SQS queue is located

Available Actions

Send Message to Queue

Sends a message to a specified SQS queue. Messages are durably stored and can be processed asynchronously
by consumers polling the queue.

Features:

• Support for message delays (0-900 seconds)
• Message attributes for metadata
• Support for both standard and FIFO queues
• Automatic message deduplication (FIFO queues)

Rate Limiting and Error Handling

SQS has the following limits:

• Standard queues: Nearly unlimited throughput
• FIFO queues: 300 messages/second (batched) or 3000 messages/second (unbatched)
• Maximum message size: 256 KB

The connector includes built-in handling for AWS throttling and service availability:

• Automatic backoff and retry for throttling errors (HTTP 429, RequestThrottled)
• Automatic backoff and retry for service unavailable errors (HTTP 503, ServiceUnavailable)
• Exponential backoff strategy with configurable retry intervals
• Respects AWS throttling recommendations for optimal retry timing

Common Use Cases

• Trigger background processing workflows
• Decouple microservices and distributed systems
• Buffer high-volume requests during traffic spikes
• Implement event-driven architectures
• Queue tasks for batch processing
• Integrate with AWS Lambda for serverless processing