> ## Documentation Index
> Fetch the complete documentation index at: https://docs.draftt.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Redis Cloud

Connect your Redis Cloud account to Draftt to monitor Redis deployments, track version currency, and stay ahead of maintenance tasks.

## Prerequisites

* A Redis Cloud account with permissions to create API keys
* Access to the Draftt dashboard (**Integrations > Redis Cloud**)

## Setup

<Steps>
  <Step title="Create an API User Key">
    1. Log in to the [Redis Cloud console](https://app.redislabs.com)
    2. Go to **Access Management > API Keys**
    3. Click the **+** icon to create a new API User Key
    4. Enter the key name: `draftt-api-key`
    5. In the **Select User** field, choose an existing user or create a new one

    <Tip>
      We recommend assigning the user the **Viewer** role only. Draftt only needs read access.
    </Tip>

    6. Click **Create** and copy the generated key
  </Step>

  <Step title="Copy your API Account Key">
    On the same API Keys page, copy your **API Account Key** using the copy button.
  </Step>

  <Step title="Enter the keys in Draftt">
    In the Draftt setup dialog, paste the **API User Key** and **API Account Key**, then click **Create**.
  </Step>
</Steps>

## What Draftt Reads

Draftt's API keys have **read-only** access. They cannot create, modify, or delete any resources in your Redis Cloud environment.

Draftt monitors your Redis subscriptions, database versions, configuration settings, and maintenance windows.

## Verifying Your Connection

After setup, return to **Integrations > Redis Cloud** in Draftt. The connected account shows a status:

* **Healthy** -- Draftt can access your Redis Cloud data as expected.
* **Unhealthy** -- Check that the API keys have not been revoked and the associated user has the Viewer role.

## Troubleshooting

**Authentication fails:** Verify both the API User Key and API Account Key are correct. These are two separate keys -- make sure you haven't swapped them.

**No data appearing:** Confirm the user associated with the API key has at least Viewer permissions on the subscriptions you expect to see.
