AWS SQS Source Connection for Real-Time Journeys

Connect GrowthLoop to an AWS SQS queue when your events are published to SQS instead of Kafka or Pub/Sub.

Configure the connection

Go to the Organization page → Source Connections → New Source Connection.
Select AWS SQS.
Fill out the required details:

Field Name	Required	Description
Name	Yes	Descriptive name for the SQS connection.
Description	No	Optional context about the queue.
Queue URL	Yes	Full URL of the SQS queue.
AWS Region	Yes	Region where the queue is hosted (e.g., `us-east-1`).
AWS Access Key ID	Yes	IAM access key with permission to read from the queue.
AWS Secret Access Key	Yes	Secret key associated with the access key.
AWS Queue Type	Yes	`standard` or `fifo` (FIFO queues must end with `.fifo`).

AWS permissions (required)

The AWS credentials must include at least:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "sqs:ReceiveMessage",
        "sqs:DeleteMessage",
        "sqs:GetQueueAttributes"
      ],
      "Resource": "arn:aws:sqs:<REGION>:<ACCOUNT_ID>:<QUEUE_NAME>"
    }
  ]
}

You may optionally grant sqs:ChangeMessageVisibility if long processing times are expected.

Operational notes

Ensure the queue visibility timeout is long enough for message processing.
FIFO queues require exactly-once semantics and proper deduplication settings.
Use least-privilege IAM users or roles and rotate credentials regularly.

Click Create to validate credentials and test the connection.

👍
Success
You've configured an AWS SQS source connection. Next, register a real-time event.