> 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/operations/upgrades/rotating-keys.md).

# Rotating keys

Rotating keys for custom buckets, OAuth connections, basemaps, and API keys

Rotating keys in CARTO Self-Hosted is a simple process to ensure the security of your custom buckets, BigQuery OAuth connections, Google basemaps and custom LDS API Keys.

{% tabs %}
{% tab title="Kots" %} <img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-9eca52f0d85c9aacba5a62150e03b4faee188bd8%2Ftool-kots.svg?alt=media" alt="Kots" width="18">

1. Access the Admin Console and check the config used to deploy your CARTO Self-Hosted platform.
2. Update the keys related to [custom buckets](/carto-self-hosted/configuration/data-and-storage/configure-your-own-buckets.md), [BigQuery OAuth connections](/carto-self-hosted/configuration/security/enable-bigquery-oauth-connections.md), [Google basemaps](/carto-self-hosted/configuration/basemaps/enable-google-basemaps.md) and LDS API Keys.
3. Update your Self-Hosted installation to apply the changes.
   {% endtab %}

{% tab title="Helm" %} <img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-ba881227fa0a4e04d6d1ddbe193d0e0de6876521%2Ftool-helm.svg?alt=media" alt="Helm" width="18">

#### If you've provided redacted secrets values:

1. Access the <mark style="color:orange;">customizations.yaml</mark> file used to deploy your CARTO Self-Hosted platform.
2. Update the keys related to [custom buckets](/carto-self-hosted/configuration/data-and-storage/configure-your-own-buckets.md), [BigQuery OAuth connections](/carto-self-hosted/configuration/security/enable-bigquery-oauth-connections.md), [Google basemaps](/carto-self-hosted/configuration/basemaps/enable-google-basemaps.md) and LDS API Keys.
3. Save the changes to the <mark style="color:orange;">customizations.yaml</mark> file.
4. Upgrade your Self-Hosted installation to apply the changes.

**If you need to update secrets manually:**

1. Identify the secrets associated with [custom buckets](/carto-self-hosted/configuration/data-and-storage/configure-your-own-buckets.md), [BigQuery OAuth connections](/carto-self-hosted/configuration/security/enable-bigquery-oauth-connections.md), [Google basemaps](/carto-self-hosted/configuration/basemaps/enable-google-basemaps.md) and LDS API Keys.
2. Use the `kubectl` command to update the specific secrets.
3. Upgrade your installation to apply the changes.
   {% endtab %}
   {% endtabs %}

Remember to perform these steps with caution, ensuring minimal downtime for your CARTO Self-Hosted deployment.

## Post-rotation verification

After rotating keys, confirm the deployment is still healthy:

* [ ] All pods are in `Running` or `Completed` state
* [ ] The CARTO application is reachable and you can log in
* [ ] Object storage (blob buckets) is accessible (thumbnails load, imports work)
* [ ] Data warehouse connections are healthy (especially BigQuery OAuth connections)
* [ ] Google Basemaps render correctly (if enabled)


---

# 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.carto.com/carto-self-hosted/operations/upgrades/rotating-keys.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.