Why does my SQS destination fail to connect?

When configuring an SQS destination, the region you enter must match the region in your queue URL.

When configuring an SQS destination, the region you enter must match the region in your queue URL. A queue at sqs.us-east-1.amazonaws.com must be configured as us-east-1; a wrong-endpoint connection error usually means a region mismatch.

SQS messages cap at 256KB, and most data payloads (especially activity and daily) exceed that, so full payloads cannot ride inline.

The supported pattern is S3 plus SQS: the payload is written to an S3 bucket (Terra-hosted by default, or your own on request) and the SQS message of type s3_payload carries a pre-signed URL/reference to it.

If you need payloads inline, use a webhook destination instead.