> 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/api-reference/databases/v2/overview.md).

# Overview

The IONOS CLOUD DBaaS In-Memory DB v2 API (2.0.0) provides a fully managed in-memory cluster service for high-performance caching, real-time analytics, and message brokering workloads. It features a unified Cluster resource model, in-place version upgrades without reprovisioning, and dedicated Snapshot Locations for geographic data safety compared to the v1 API. If you're new to the In-Memory DB v2 API, see [Quick Start](#tag/Quick-Start). If you're migrating from v1, see [In-Memory DB API Versions](#tag/In-Memory-DB-API-Versions).

### What Can You Do with the In-Memory DB v2 API?

The IONOS CLOUD [In-Memory DB v2 API](#tag/Overview) provides a single API surface for the full lifecycle of in-memory clusters. Using the v2 API, you can:

* **Provision and modify clusters:** Create or update fully managed in-memory clusters using the idempotent Ensure pattern (`PUT` semantics) on region-specific endpoints.
* **Manage credentials:** Create or update database users directly as part of the cluster resource, with no separate user management endpoint needed.
* **Restore from snapshots:** Provision a new cluster pre-populated with data from an existing snapshot, or restore in-place on an existing cluster, using the `restoreFromSnapshot` property. Restore from the latest snapshot, or set `recoveryTargetDatetime` to restore from the most recent snapshot at or before a chosen time.
* **Control geographic data safety:** Query dedicated Snapshot Locations to specify exactly where cluster snapshots are stored.
* **Query supported configurations:** Retrieve centralized lists of supported DBaaS versions to plan and configure cluster deployments.

### Endpoints

The In-Memory DB v2 API is available at the following regional endpoints.

| **Location**              | **Region** | **Endpoint**                               |
| ------------------------- | ---------- | ------------------------------------------ |
| Frankfurt, Germany        | `de-fra`   | `https://in-memory-db.de-fra.ionos.com/v2` |
| Berlin, Germany           | `de-txl`   | `https://in-memory-db.de-txl.ionos.com/v2` |
| Logroño, Spain            | `es-vit`   | `https://in-memory-db.es-vit.ionos.com/v2` |
| Worcester, United Kingdom | `gb-bhx`   | `https://in-memory-db.gb-bhx.ionos.com/v2` |
| London, United Kingdom    | `gb-lhr`   | `https://in-memory-db.gb-lhr.ionos.com/v2` |
| Newark, United States     | `us-ewr`   | `https://in-memory-db.us-ewr.ionos.com/v2` |
| Las Vegas, United States  | `us-las`   | `https://in-memory-db.us-las.ionos.com/v2` |
| Lenexa, United States     | `us-mci`   | `https://in-memory-db.us-mci.ionos.com/v2` |
| Paris, France             | `fr-par`   | `https://in-memory-db.fr-par.ionos.com/v2` |

### Features

* **Replication modes:** In-Memory DB supports standalone mode (a single node) and replicated mode (one primary node and up to four passive secondary nodes that use asynchronous replication). The replication mode is determined by the `instances` count you specify when you provision the cluster.
* **Ensure pattern:** `PUT` operations use full-replacement semantics. All required cluster fields must be present in every `PUT` request. If you omit `credentials`, the existing credentials are kept.
* **Version upgrades:** Only in-place upgrades are supported. You can upgrade by setting a new version value in a `PUT` request using a version listed in `canUpgradeTo`. Downgrades are not supported.

### Benefits

* **Improved upgrade experience:** In-place version upgrades eliminate cluster recreation and data migration. You can upgrade without application reconfiguration downtime.
* **Geographic data safety:** Snapshot Locations let you store snapshots in a separate region from your cluster, reducing the impact of regional incidents on your data.
* **Automatic credential management:** The API creates or updates database users automatically when you submit credentials. You don't need to check whether a user exists before submitting.
* **Faster failure diagnosis:** The `statusMessage` field surfaces the failure reason directly in the API response. You can identify and resolve issues without additional API calls.
* **Predictable storage allocation:** Storage is automatically derived from RAM and persistence mode. You don't need to pre-calculate or size disk capacity separately.

To authenticate with the API, see [Authentication](#tag/Authentication). To make your first API call, see [Quick Start](#tag/Quick-Start).


---

# 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/api-reference/databases/v2/overview.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.