> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview-1/gcp-services/gcp-databases/managed-redis.md).

# Managed Redis

Support for Redis database instances

DuploCloud supports Redis database instances. Redis stands for Remote Dictionary Server and is a fast, open-source, in-memory, key-value data store. Redis can function as a database, cache, message broker, and queue.

Redis delivers sub-millisecond response times, enabling millions of requests per second for real-time applications.

## Adding a Redis database instance

1. In the DuploCloud Portal, navigate to **Cloud Services** -> **Redis**.
2. Click **Add**. The **Add Redis Instance** page displays.

<div align="left"><figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FLWZqGqx01jg0wUZHc2F7%2Fscreenshot-nimbusweb.me-2024.02.15-12_22_23.png?alt=media&amp;token=228c9f35-5c81-4a63-a057-5da92bbcc1b9" alt=""><figcaption><p><strong>Add Redis Instance</strong> page</p></figcaption></figure></div>

3. Enter the database **Name**.
4. In the **Display Name** field, enter a useful database name for reference.
5. From the **Tier** list box, select **Basic** for a Tier0 standalone instance; select **Standard** for a Tier1 High Availability primary/replica instance.
6. In the **Memory Size** field, enter memory size in gigabytes (GB).
7. In the **Redis Config** field, specify the Redis configuration.
8. In the **Labels** field, specify `key`/`value` pairs.
9. Select **Enable Auth and Security** to enable OSS Redis AUTH for the Redis instance.
10. Select Enable **Encryption-in-Transit** to select the TLS mode of the Redis instance.
11. Click **Create**. The Redis database **Details** tab displays on the **Redis** tab with **Connectivity**, **General**, and **Security** cards.

<div align="left"><figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FNp0cKzBgP1iqsAL4GsJG%2Fscreenshot-nimbusweb.me-2024.02.15-12_26_37.png?alt=media&amp;token=6125ed7f-87e7-4be3-aab5-755257ebe1eb" alt=""><figcaption><p><strong>Details</strong> tab for a Redis database instance</p></figcaption></figure></div>


---

# 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.duplocloud.com/docs/automation-platform/overview-1/gcp-services/gcp-databases/managed-redis.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.
