FAQ

Fundamentals

How can I change my user password?

Unfortunately, updating your password is not currently possible.

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 In-Memory DB documentation.

How do you distinguish between supported and unsupported features?

According to the In-Memory DB documentation, stack features that display their logo are not supported.

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

Unfortunately, IONOS CLOUD 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 Determine Provisioned Block Storage in an In-Memory DB Cluster.

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 In-Memory DB v2 Cloud API.

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 Authentication API.

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 Create Cluster or Ensure Cluster, 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.