> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-self-hosted/configuration.md).

# Configuration Guides

After deploying CARTO Self-Hosted, use these guides to configure specific aspects of your installation. Each guide includes instructions for both Kots and Helm deployment methods where applicable.

{% hint style="info" %}
New to how configuration works? Read [How Configuration Works](/carto-self-hosted/concepts/configuration-management.md) first — it explains the Helm (file-based) and Kots (Admin Console) models and where your settings live. For managing it safely, see [Manage configuration as code](/carto-self-hosted/best-practices/operations/operations-best-practices.md#manage-configuration-as-code).
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Networking &#x26; Publishing</strong></td><td>Load balancing, forward proxy, custom domains, and TLS configuration.</td><td><a href="/pages/MrZ9Wi62a67sSUwiziVL">/pages/MrZ9Wi62a67sSUwiziVL</a></td></tr><tr><td><strong>Data &#x26; Storage</strong></td><td>Object storage buckets, in-memory cache, CARTO Data Warehouse, and Redshift imports.</td><td><a href="/pages/qIkedsrC9jPxEt1psKME">/pages/qIkedsrC9jPxEt1psKME</a></td></tr><tr><td><strong>Security &#x26; Cloud Identities</strong></td><td>SSO, service accounts, Workload Identity, Pod Identity, and BigQuery OAuth.</td><td><a href="/pages/XLAE0NORHsmTiAvGNDq8">/pages/XLAE0NORHsmTiAvGNDq8</a></td></tr><tr><td><strong>Performance &#x26; HA</strong></td><td>High availability configuration and performance tuning.</td><td><a href="/pages/sB7Obekw1zSpwtixbdJk">/pages/sB7Obekw1zSpwtixbdJk</a></td></tr><tr><td><strong>AI Features for Agentic GIS</strong></td><td>Configure the infrastructure prerequisites for CARTO AI features.</td><td><a href="/pages/1mcbsUinesqHqa5thXbw">/pages/1mcbsUinesqHqa5thXbw</a></td></tr><tr><td><strong>Basemaps</strong></td><td>Configure basemap providers, such as Google Maps.</td><td><a href="/pages/MDlixzxpuCvcR5fe71IK">/pages/MDlixzxpuCvcR5fe71IK</a></td></tr><tr><td><strong>Usage Tracking</strong></td><td>Track activity data from public maps in your deployment.</td><td><a href="/pages/F44ERlbjHrNpfZQUeidO">/pages/F44ERlbjHrNpfZQUeidO</a></td></tr></tbody></table>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.carto.com/carto-self-hosted/configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.