> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/databases/in-memory-db/in-memory-db-faqs.md).

# FAQ

## Fundamentals

### What is IONOS CLOUD In-Memory DB?

<code class="expression">space.vars.ionos\_cloud</code> DBaaS for In-Memory DB is a fully managed, in-memory data structure store compatible with the Redis® OSS API. In-Memory DB v2 is based on [<mark style="color:blue;">Valkey</mark>](https://valkey.io/). It combines an in-memory data store with a dynamic, real-time database, and can be used as a dedicated in-memory data store, a real-time database service, a dedicated in-memory data store, a message broker, or a streaming engine. For more information, see the [<mark style="color:blue;">Overview</mark>](/cloud/databases/in-memory-db/overview.md).

### Is any installation required to use In-Memory DB?

No. You can order and manage an In-Memory DB cluster through the Data Center Designer (DCD), the API, or automation tools such as Ansible and Terraform. To connect to your instance, use `redis-cli` or a Redis®-compatible client driver, optionally over a [<mark style="color:blue;">TLS</mark>](https://redis.io/docs/latest/operate/rs/security/encryption/tls/enable-tls/)-secured connection.

### Which versions of In-Memory DB are available?

In-Memory DB v2 clusters support Valkey versions **9**, **8.1**, and **8**. In-Memory DB v1 instances default to Redis version **7.2**.

### On what server instances is In-Memory DB offered?

In-Memory DB runs exclusively on **Dedicated Core** infrastructure; the CPU type cannot be changed.

### As a managed service, which tasks does IONOS CLOUD handle?

<code class="expression">space.vars.ionos\_cloud</code> handles database management through the DCD or the DBaaS API, regular patches and upgrades during maintenance windows, automated snapshots or backups (depending on your cluster version) for disaster recovery, and service monitoring for both the cluster and the underlying infrastructure.

### What remains my responsibility while using In-Memory DB?

Tasks related to the optimal health of your In-Memory DB cluster remain your responsibility, including optimization, organizing data, and updating statistics. For more information, see [<mark style="color:blue;">Platform tasks</mark>](/cloud/databases/in-memory-db/overview.md#platform-tasks).

### How can I change my user password?

You cannot change the password through the DCD. Using the In-Memory DB v2 API, you can update a user's password by including it in the `credentials` property of a `PUT /clusters/{clusterId}` request; the password is updated if the user already exists. For more information, see [<mark style="color:blue;">How are credentials and passwords managed in the In-Memory DB v2 API?</mark>](#how-are-credentials-and-passwords-managed-in-the-in-memory-db-v2-api).

### What user permissions do I get?

You have access to all command categories; however, within the "dangerous" category, permissions are limited to the `INFO`, `KEYS`, and `SORT` commands only. For more information, refer to the [<mark style="color:blue;">In-Memory DB documentation</mark>](https://redis.io/docs/latest/operate/oss_and_stack/management/security/acl/#command-categories).

### How do you distinguish between supported and unsupported features?

According to the [<mark style="color:blue;">In-Memory DB documentation</mark>](https://redis.io/docs/latest/), stack features that display their logo are not supported.

### Does IONOS CLOUD DBaaS use or provide support for an In-Memory DB Sentinel?

Unfortunately, <code class="expression">space.vars.ionos\_cloud</code> does not use or provide support for an In-Memory DB Sentinel. However, we offer monitoring and automatic failover features.

### Can I customize my cluster's Block Storage capacity?

The provisioned Block Storage in an In-Memory DB cluster depends on the amount of RAM configured and the data persistence mode selected. As a result, you cannot select the amount of Block Storage for your cluster; instead, they are calculated automatically following a pre-determined ratio. For more information, see [<mark style="color:blue;">Determine Provisioned Block Storage in an In-Memory DB Cluster</mark>](/cloud/databases/in-memory-db/overview/data-persistence.md#determine-provisioned-block-storage-in-an-in-memory-db-cluster).

## Provisioning and configuration

### How many instances can an In-Memory DB v2 cluster have?

A cluster can have between 1 and 5 instances. A value of 1 creates a standalone instance; values 2–5 create a replicated setup with one primary and n-1 passive secondaries.

### Which replication mode does In-Memory DB v2 use?

Replication between the primary and secondary instances is always asynchronous. The replication mode is not configurable.

### How do I migrate an existing v1 cluster to v2?

Migration is not automatic. The v1 clusters must be migrated manually through the API before v1 is decommissioned. For step-by-step guidance, see [<mark style="color:blue;">Migrate from In-Memory DB v1 to v2</mark>](/cloud/databases/in-memory-db/how-tos/migrate-from-v1-v2.md).

## Backup and recovery

### Can I restore an existing In-Memory DB cluster from the DCD?

No. In the DCD, restoring from a snapshot is only available while creating a new cluster, through the **Restore configuration** section. For more information, see [<mark style="color:blue;">Restore an In-Memory DB Cluster</mark>](/cloud/databases/in-memory-db/how-tos/v2/restore-in-memory-db-cluster.md). To restore an existing cluster's data in place, use the v2 API's `restoreFromSnapshot` property in a `PUT /clusters/{clusterId}` request.

## In-Memory DB v2 API

### What is the In-Memory DB v2 API?

The In-Memory DB v2 API is a fully managed, high-performance `REST` API for provisioning and managing In-Memory DB clusters, supporting caching, real-time analytics, and message brokering workloads. It renames the primary resource from `ReplicaSet` to `Cluster`, introduces dedicated `Versions` and `SnapshotLocations` endpoints, adds inline snapshot restore, hashed password credentials, and built-in observability controls. For more information, see [<mark style="color:blue;">In-Memory DB v2 Cloud API</mark>](https://api.ionos.com/docs/in-memory-db/v2/).

### What authentication method is required for the In-Memory DB v2 API?

The v2 API requires API token authentication (`tokenAuth`). You must include a valid token in the `Authorization` header of every request. For information on generating tokens, see the [<mark style="color:blue;">Authentication API</mark>](https://api.ionos.com/docs/authentication/v1/#tag/tokens/operation/tokensGenerate).

### What is the "Ensure" pattern in the In-Memory DB v2 API?

The v2 API uses `PUT /clusters/{clusterId}` as an idempotent "Ensure" operation — it creates the cluster if it does not exist, or updates it to match the provided payload if it does. Fields omitted from the request are filled with defaults rather than inheriting their previous values.

### How are credentials and passwords managed in the In-Memory DB v2 API?

Credentials are managed through the `credentials` property on the cluster resource. When included in a `PUT` request, the specified user is created if they do not exist, or their password is updated if they do. Omitting credentials leaves them unchanged. Passwords must be submitted as a pre-hashed `SHA-256` value — a 64-character lowercase hexadecimal string. Base64-encoded SHA-256 hashes are not accepted.

### How are snapshots managed in the In-Memory DB v2 API?

Snapshot behaviour is configured through the `snapshot` property on the cluster resource. You can set the Object Storage `location` where snapshots are stored, a `retentionDays` value (1–365 days, defaulting to 7), and a `snapshotHours` array specifying the UTC hours at which scheduled snapshots are taken. An empty `snapshotHours` array disables scheduled snapshots. Use `GET /snapshot-locations` to retrieve the list of valid storage locations.

### How do I restore a cluster from a snapshot in the v2 API?

Restore is performed inline — there is no separate Restore endpoint in v2. Include the `restoreFromSnapshot` field with the `sourceSnapshotId` UUID in the `POST /clusters` body to initialize a new cluster from a snapshot, or in a `PUT /clusters/{clusterId}` body to overwrite an existing cluster's data in place. Only snapshots from clusters in the same region are eligible. For in-place restores, the cluster may experience a brief period of downtime.

### Does the In-Memory DB v2 API support filtering and pagination?

Yes. All listing endpoints support pagination through `offset` and `limit` parameters (maximum 1000 per page). The `GET /clusters` endpoint supports `filter.name` (case-insensitive substring match) and `filter.state` filters. The `GET /snapshots` endpoint supports `filter.clusterId` to scope results to a specific cluster.

### How do I activate logs and metrics for my cluster?

In [<mark style="color:blue;">Create Cluster</mark>](https://api.ionos.com/docs/in-memory-db/v2/#tag/Clusters/operation/clustersPost) or [<mark style="color:blue;">Ensure Cluster</mark>](https://api.ionos.com/docs/in-memory-db/v2/#tag/Clusters/operation/clustersPut), set `logsEnabled` to `true` to enable log collection and `metricsEnabled` to `true` to enable metrics collection. If the Observability service is not activated on your contract, the setting is accepted but has no effect until the service is activated.


---

# 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.ionos.com/cloud/databases/in-memory-db/in-memory-db-faqs.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.