> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/webhook/storage-destinations-s3-sqs-supabase-sql-gcs/sqs-region-and-message-size.md).

# Why does my SQS destination fail to connect?

When configuring an [SQS destination](https://docs.tryterra.co/health-and-fitness-api/integration-setup/setting-up-data-destinations/queuing-services-sqs-kafka), **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](https://docs.tryterra.co/health-and-fitness-api/integration-setup/setting-up-data-destinations/webhooks) instead.