> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings/custom-aws-endpoint-urls.md).

# Configuring endpoint URLs for calls to AWS

For calls to AWS products that are used in Textual, you can configure custom URLs to use. For example, if you use proxy endpoints, then you would configure those endpoints in Textual.

The [environment variables](/textual/textual-install-administer/configuring-textual/textual-env-var-configure.md) for custom AWS endpoints include the following:

* `AWS_S3_FORCE_PATH_STYLE` - Whether to always use path-style instead virtual-hosted-style for connections to Amazon S3. The default is `false`.

  This setting is only used if you configured either `AWS_ENDPOINT_URL` or `AWS_ENDPOINT_URL_S3`.
* `AWS_ENDPOINT_URL` - The URL to use for all AWS calls, including calls to Amazon S3, Amazon Textract, and Amazon SES v2. This global endpoint is overridden by service-specific endpoints.
* `AWS_ENDPOINT_URL_S3` - The URL to use for calls to Amazon S3. This overrides the global URL set in `AWS_ENDPOINT_URL`.
* `AWS_ENDPOINT_URL_TEXTRACT` - The URL to use for calls to Amazon Textract. This overrides the global URL set in `AWS_ENDPOINT_URL`.
* `AWS_ENDPOINT_URL_SESV2` - The URL to use for calls to Amazon SES v2. This overrides the global URL set in `AWS_ENDPOINT_URL`.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/textual/textual-install-administer/configuring-textual/general-instance-and-processing-settings/custom-aws-endpoint-urls.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.