> 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/webhook/storage-destinations-s3-sqs-supabase-sql-gcs/sqs-region-and-message-size.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.