In-Memory DB instances

• Single-node instance: A single-node instance only has one "primary node". This node accepts customer connections and performs read and write operations. It is a single point of truth and a single point of failure.

• Multi-node instance: A multi-node instance contains one "primary node" and one or more "secondary nodes" replicating data from the primary node. The secondary nodes always attempt to keep up-to-date with the primary, but they may lag due to the asynchronous replication. If the current primary node fails, a secondary node elevates to the primary node. The old primary node is automatically fixed and turned secondary.

In-Memory DB instance scaling

You can scale the existing In-Memory DB instances using "horizontal" and "vertical" scaling.

Replication modes for high availability

The synchronization_mode determines how transactions are replicated between multiple nodes before a transaction is confirmed to the client. IONOS DBaaS supports the following replication modes for In-Memory DB: Asynchronous (default) and Semi-Synchronous. In either mode, In-Memory DB commits the transaction first on the primary and then replicates to the standby secondary node(s).

Asynchronous replication

However, In-Memory DB has a built-in asynchronous replication mode, which does not wait for the standby before confirming a transaction back to the user. Transactions are confirmed to the client after being written to disk on the primary node. Replication takes place in the background. In asynchronous mode, the instance is allowed to lose some committed (not yet replicated) transactions during a failover to ensure availability.

The benefit of asynchronous replication is the lower latency. The downside is that recent transactions might be lost if standby is promoted to the primary node. The lag between the primary and secondary nodes tends to be a few milliseconds.

Semi-synchronous replication

For semi-synchronous replication, you can use the WAIT command. This is particularly useful to prevent data loss if the primary node goes down after acknowledging but before replicating the write operation. Executing the command blocks the client until all pending write operations are transferred and acknowledged by the specified replicas. For more information, refer to the In-Memory DB documentation.

With IONOS Cloud DBaaS, you can quickly set up and manage In-Memory DB, an open-source and in-memory data structure store that stores key-values, and is compatible with the Redis® OSS API. This capability makes it a versatile choice for various applications such as databases, caches, message brokers, or streaming engines.

The IONOS DBaaS offering for In-Memory DB delivers a fully managed service combined with an in-memory cache while also serving as a dynamic real-time database service. This combination leverages memory's rapid access speeds, ensuring high performance. It is particularly well-suited for frequently accessed data that rarely changes, allowing for significant reductions in the load on central databases through efficient in-memory caching.

You can initiate In-Memory DB via the DCD, APIs or automation tools like Ansible and Terraform.

Product Overview

In-Memory DB

Quick Links

Developer Tools

Frequently Asked Questions (FAQs)

To get answers to the most commonly encountered questions about In-Memory DB, see FAQs.

Features

• In-memory data structure store: In-Memory DB can be used as a data structure, cache, message broker, and streaming engine.

• Multiple data types and structures: While technically In-Memory DB is a key-value store, it is also a data structure server that supports multiple data types and structures, including the following: strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

• Key eviction policy: In-Memory DB supports LRU key eviction policy, which automatically detects old data in the cache when the maxmemory limit is reached upon incorporating new data. For more information, refer to the .

• Lua Scripts: You can upload and execute Lua scripts to the In-Memory DB server. These scripts can use programmatic control structures and supported commands to access the In-Memory DB instance during execution.

• Built-in asynchronous replication: Its built-in asynchronous replication feature acknowledges the amount of data processed. For more information, refer to the .

• On-disk persistence: It persists data on disks using AOF and RDB persistence options.

• User Management and Security: Access to the instance can be restricted to authorized users only. Role-based access control, robust encryption support, and user management tools ensure secure access and data protection.

IONOS DBaaS Features

• Upgrades: IONOS DBaaS supports user-defined maintenance windows with minimal service disruption. The In-Memory DB instance may be unreachable for a few seconds when necessary for restarts or switching to another replica. Single-node instances temporarily gain a second node when it is necessary to replace the old one. Hence, maintenance downtime is the same for multi-node and single-node instances.

• Programmatic Resource Management: Easier to deploy and manage In-Memory DB in the IONOS Cloud ecosystem through APIs, SDKs, and configuration management tools.

• Monitoring and Reporting: In-Memory DB provides tools for performance monitoring, query analysis, and reporting to help optimize instance usage and identify potential issues.

• Restore backup files: You can restore the backup files of each In-Memory DB cluster. For more information, see .

Benefits

• Easy Configuration: Configure your In-Memory DB instance to comply with IONOS DBaaS's specifications. You can quickly create an instance and define users using the API commands.

• Swift data retrieval: Its in-memory data structure store allows quick data retrieval from the cache.

• Scalable: Because of In-Memory DB's vertical scalability, you can add storage, memory, and cores to match the growing demand for greater data processing power.

• High availability: It supports both multi-node and single-node instances, which are equipped with automatic node failure handling. This ensures that it can continue to operate smoothly even if one or more nodes fail.

• Security: If your In-Memory DB instance is configured to use TLS, clients and In-Memory DB communicate securely using TLS. For more information, refer to the following sections of the In-Memory DB documentation:
• Resources: It is offered on Enterprise VM, with a dedicated CPU, storage, and RAM. Currently, SSD is the only supported storage option for In-Memory DB.

• Network: To guard against direct internet-based threats, DBaaS is only connected to private networks.

In-Memory DB is a key-value structure-based in-memory data storage. Data is stored in Random-Access Memory (RAM) instead of a disk and is swiftly accessible. Rapid access to data is provided by RAM, as opposed to a disk.

IONOS DBaaS for In-Memory DB is a fully managed service, compatible with legacy Redis® OSS, that gives you access to the capabilities of its data structures. It can be used as a dedicated in-memory cache and a real-time database service. This combination of services enables In-Memory DB to deliver greater performance.

It is simpler to configure your In-Memory DB instance with IONOS DBaaS. You get access to a secure, dedicated In-Memory DB server managed by IONOS. DBaaS gives you access to the capabilities of the In-Memory DB data structures, which means that you can use the same code, applications, and tools you already use in your existing databases. You can use the In-Memory DB features, such as patching the In-Memory DB data structures, creating backups and redundancy, and enhancing security with IONOS DBaaS.

When used as a cache, In-Memory DB accelerates data access from primary instances and associated data stores with minimal latency. This is quicker as compared to interacting with a traditional database. In-Memory DB acts as a caching layer, thus, speeding up the API response time and data retrieval.

In-Memory DB supports data persistence by writing data into long-lasting storage. For more information, see .

It is mandatory to specify a periodic maintenance time window for regular maintenance. During the maintenance time window, you may encounter a short, occasional downtime, typically caused by restarting In-Memory DB or switching to another replica.

Provisioning a new In-Memory DB instance via a fully managed IONOS DBaaS is faster than self-managed manual procurement, configuration, and installation of In-Memory DB on local hardware. Software patching and upgrades are performed automatically by DBaaS.

The illustration shows how In-Memory DB instances can be created and managed using IONOS DBaaS.

Supported versions

In-Memory DB is compatible with legacy Redis® OSS stable version 7.2.

Locations

DBaaS for In-Memory DB is offered in all IONOS Cloud locations. You can use DBaaS instances running In-Memory DB in the IONOS Cloud infrastructure.

Security

IONOS Cloud updates and patches your In-Memory DB instance to achieve high standards of functionality and security. This includes minor patches for In-Memory DB and patches for the underlying operating system. Generally, these updates are unnoticeable and do not interrupt your operation. However, occasionally, IONOS restarts your In-Memory DB instance to allow the changes to take effect.

Prerequisites

• Prepare for a downtime during the version upgrade.

• Ensure the instance has enough available storage. While the upgrade is space-efficient (because it does not copy the data directory), some temporary data is written to the disk.

Currently, IONOS DBaaS only supports minor upgrades for In-Memory DB. All changes that may cause service interruption (like upgrades) are executed within the maintenance window, which is a weekly four-hour window. During the maintenance window, you may experience uncontrolled disconnections and an inability to connect to the In-Memory DB instance. Such disconnections are destructive for any ongoing transactions and we recommend that you reconnect.

You can configure a maintenance window during the In-Memory DB instance creation using the same API request. For more information, see . You can also configure one when you modify the existing In-Memory DB instance. For more information, see .

The following code schedules automatic maintenance every Monday at 16:30:59:

In-Memory DB supports various persistence options. For more information, refer to the .

IONOS DBaaS completely supports a requirements-based persistence mechanism for In-Memory DB. You can either choose to use In-Memory DB (RDB) and Append-Only File (AOF) data persistence options or combine both for durable storage. Contextually, data persistence refers to the information saved on a reliable non-volatile storage medium (for example, memory, HDD, or SSD) that can be recovered even during a system failure. Hence, persistent data—or non-volatile storage—can save data that is still accessible even during a crash.

RDB

An RDB is a compact single file called a snapshot, representing your In-Memory DB data in a binary format. Due to its compactness, storage of In-Memory DB data is quicker, and retrieval is swifter. IONOS DBaaS periodically writes In-Memory DB in-memory data to disk files with the .rdb file extensions, thus creating multiple snapshot files for each write operation. In-Memory DB writes the entire point-in-time view of the dataset to the persistent storage.

The default RDB settings for snapshots are as follows:

• every one hour for a single change or write operation.

• every five minutes for at least 100 write operations.

• every minute for at least 10000 write operations.

DBaaS clears In-Memory DB in-memory data soon after creating a snapshot on the disk. Because it is automated and periodic, the write operation will lessen your workload and resume activities quickly in case of a failure. During a system crash, you can select from multiple snapshot files stack and restore the appropriate version. You can also back it up to a .

AOF

In-Memory DB provides another data persistence option called the AOF, which logs all its data into a log file. Every time In-Memory DB performs a write operation, it appends it to the AOF file. The AOF file is saved with a .aof extension and can be used to recover the entire replicaset in case of a crash. You can use the file to reconstruct the original dataset during a server restart.

In-Memory DB automatically rewrites an AOF file in the background when it reaches its maximum capacity, compacting it to save just the most recent data version.

Benefits of RDB and AOF combination

• Regular backups of the In-Memory DB dataset.

• Secondary instances can use the RDB and AOF files to rebuild the dataset from the primary instance during replication.

• The restart time is faster than recreating the dataset from scratch, thus enhancing the performance, scalability, and reliability.

Determine Provisioned Block Storage in an In-Memory DB Cluster

The provisioned Block Storage in an In-Memory DB cluster depends on the amount of RAM configured and the data persistence mode selected.

The amount of provisioned Block Storage is based on the relationship below:

You get access to all command categories, except the commands that are listed in the "dangerous" category. For more information, refer to the .

DBaaS services offered by IONOS Cloud

All back-end tasks necessary to keep your In-Memory DB instance operating at peak efficiency are handled by the IONOS platform. You can perform the following:

• Pre-set instance configuration and configuration management options.

• Automated backups for seven days.

• Regular patches and upgrades during maintenance.

• Disaster recovery via automated backup only if persistence is configured. For more information, see .

• Service monitoring both for the In-Memory DB instance and the underlying infrastructure.

Administration

Tasks related to the optimal health of the In-Memory DB instance remain your responsibility. These include:

• Optimization

• Organizing data

• Updating statistics

Quick Links

Switchover process

For administrative reasons, automatic switchovers happen in a controlled, planned manner during the scheduled maintenance. However, data is preserved during a switchover.

During a switchover, the IP address of the primary server is moved to the promoted replica server. Meanwhile, the client is signaled about the switchover by closing the TCP connection on the server. The client automatically closes the connection and reconnects to the In-Memory DB instance.

Failover process

IONOS DBaaS for In-Memory DB has an automatic failover enabled by default. A failover can occur when the primary node fails. As a result, one of the replicas is chosen and promoted to be the new primary node. When the old primary node returns, it is added as a replica of the instance.

Real-time analytics and online advertising campaigns

In-Memory DB is suitable for exceptional reliability and swift data retrieval. It stands out as the preferred choice for real-time analytics, offering seamless storage and analysis of streaming data. With its capability to process data with sub-millisecond latency, In-Memory DB significantly enhances the performance of real-time analytics applications and online advertising campaigns.

Database Caching

In-Memory DB excels at managing vast volumes of real-time data through its in-memory data storage mechanism. It efficiently groups data based on different values, such as users, time, roles, etc., and saves it in your primary database in a single transaction. This can save you time by eliminating the need for thousands of read/write operations, depending on how many queries you receive every minute; thus, facilitating the creation of highly responsive database architectures.

Leveraging In-Memory DB for caching minimizes database queries, significantly reducing traffic and the resources needed. This approach enables enhanced application performance, achieving shorter response times. Furthermore, In-Memory DB's scalable caching layer allows for rapid and cost-effective scaling, enabling organizations to develop swift applications with reduced costs.

IONOS DBaaS for In-Memory DB supports automatic backups. Automatic backups are created in either of the following instances:

• During the creation of an In-Memory DB instance.

• Upon upgrading the current version of In-Memory DB to a higher version.

IONOS DBaaS performs automatic daily full backups of the In-Memory DB instances that run regularly at a specific hour based on the value set in the DBaaS component. It ensures that there is a backup available for each day. IONOS maintains backups for the last seven days so that you can recover them for up to a week. For more information about backup restoration, see View individual cluster details and restore a backup.

You may ensure the success of creating an In-Memory DB instance by adhering to the following network and resource requirements.

Network configuration

To set up an instance inside an existing data center, you should have at least one server in a private LAN. You need to choose an IP address for the primary In-Memory DB instance to be available on your LAN within the VDC. It becomes available on the chosen IP address after provisioning.

There is currently no IP address management for In-Memory DB instances. If you use your subnet, you may use any IP address in that corresponding subnet. You must choose the IP address of the subnet that IONOS assigns you if your servers use DHCP. The IP address of the subnet can be found in your NIC configuration.

Resource considerations

CPU, RAM, storage, and the number of In-Memory DB instances are counted against quotas. For more information, see Resource allocation.

The performance of the In-Memory DB instance depends on the type of storage used. IONOS DBaaS selects the appropriate storage capacity based on the RAM size of your In-Memory DB instance and the chosen data persistence setting.

In-Memory DB instance backups

All In-Memory DB instances are backed up automatically. For more information, see Automatic backups.

The following are a few limitations that you can encounter while using In-Memory DB:

• You cannot use multiple In-Memory DB instances simultaneously, but each for a particular use case.

• You have access to ten default In-Memory DB instances, which are numbered to differentiate them. However, it is not possible to add or rename the instances after creation.

• The total upper limit for CPU cores depends on your quota. A single instance cannot exceed 16 cores.

• The total upper limit for RAM depends on your quota. A single instance cannot exceed 32 GB.

• The upper limit for storage size is 2 TB.

• Storing In-Memory DB instance backups in an IONOS S3 Object Storage is limited to the last seven days.

• The following IP ranges cannot be used with In-Memory DB services:

  • 10.208.0.0/12

  • 10.233.0.0/18

  • 192.168.230.0/24

  • 10.233.64.0/18

This topic describes connecting to the In-Memory DB instance from your managed Kubernetes cluster.

Prerequisites

Ensure that the following are available before connecting to the In-Memory DB instance:

• A datacenter with the following id: xyz-my-datacenter.

• A private LAN with id 3 using the network 10.1.1.0/24.

• A database connected to LAN 3 with the following IP address: 10.1.1.5/24.

• A Kubernetes cluster with the following id: xyz-my-cluster.

• ionosctl

Connect to the In-Memory DB Instance from the cluster

In the following example, DHCP is used to assign IP addresses to node pools. Therefore, the database must be in the same subnet as the DHCP server.

To enable connectivity, follow these steps:

1. Connect node pools to the private LAN, which is connected to the database:

ionosctl k8s nodepool create --cluster-id xyz-my-cluster --datacenter-id xyz-my-datacenter --lan-ids 3 --dhcp=true --name=my_nodepool

1. Create a pod to test the connectivity. Schedule the pod exclusively for the node pools connected to the additional LAN if you have several node pools.

# pod.yaml
apiVersion: v1
kind: Pod
metadata:
  name: connectivity-test
  labels:
    role: connectivity-test
spec:
  containers:
  - name: connectivity-test
    image: redis 
    stdin: true
    tty: true
    command:
      - "/bin/bash"

Alternatively, you can also use the following commands:

1. Create the pod using either of these commands: kubectl run redis-client --rm -it --image=redis -- /bin/bash or kubectl apply -f pod.yaml

2. Attach the pod and test connectivity:

kubectl attach -it connectivity-test
redis-cli --tls --cacert --user <USERNAME> --pass <PASSWORD> -h <DNS_NAME> PING

The In-Memory DB instance will be deployed in about five minutes after the creation of your first instance. For more information about In-Memory DB instance creation, see Create an In-Memory DB Instance.

We recommend you manually verify if the request has successfully created an instance because IONOS does not send notifications upon instance creation. However, you can poll the API to see when the state switches to AVAILABLE. You can use the following command:

while [[ $(curl -sXGET "https://in-memory-db.de-txl.ionos.com/replicasets/${UUID}" -H "Authorization: Bearer ${TOKEN}" | jq -r .metadata.state) != "AVAILABLE" ]]; do
  sleep 5
  clear
  echo -e "Cluster status:\n"
  kg replicasets "${UUID}" -ojsonpath='{.status.conditions}' | yq -P
  echo -e "\ncluster is not available yet, waiting 5 seconds..."
done

Initialize the In-Memory DB Instance

Soon after the In-Memory DB instance is created, you can establish a connection via the In-Memory DB CLI to connect it to the database. For more information, refer to the In-Memory DB documentation.

Prerequisites

• Before setting up a database, ensure that you are working within a provisioned Virtual Data Center (VDC) that contains at least one VM from which the database will be accessed. The VM you create is counted against the quota allocated in your contract.

• Database Manager is available only for contract administrators, owners, and users with Access and manage DBaaS privileges. You can set the privilege via the DCD group privileges. For more information, see Manage User Access.

Create a Cluster

To create an In-Memory DB cluster, follow these steps:

1. Log in to the DCD with your username and password.

2. Go to Menu > Databases > In-Memory DB.

1. Click Create cluster to create a new In-Memory DB cluster.

1. Enter the following details in the Create In-Memory DB Cluster window:

   • Define cluster properties

   • Select the required number of resources

   • Connect the In-Memory DB cluster with a VDC

   • Schedule cluster maintenance

   • Define users

1. Click Save to create the In-Memory DB cluster.

Define Cluster Properties

To define cluster properties, specify the following:

1. Cluster name: Enter an appropriate name for your In-Memory DB cluster.

2. Version: The value is set to 7.2, by default.

3. Instances: Enter the number of In-Memory DB nodes you want in the cluster. You can create a maximum of five nodes within a cluster. The primary In-Memory DB node always manages the data of exactly one database cluster. You can also use the arrows to increase or decrease the number of nodes. Replication is possible only when you define more than one node.

1. Replication Type: The replication type is Asynchronous by default for In-Memory DB. You will see this option only upon selecting more than one node (instance). In an asynchronous mode, the primary In-Memory DB node does not wait for a replica to indicate that the data has been written. The cluster can lose some committed transactions to ensure availability.

2. Location: Select a location of your preference from the drop-down list. The drop-down list displays the server locations where you can create clusters.

3. CPU Type: The CPU type is set to Dedicated Core, by default.

4. Persistence: Select one of the following persistence modes: In-Memory, AOF (Append Only File), RDB (Redis Database File), or RDB and AOF. For more information, see Data Persistence.

Select the required number of resources

To select the number of resources that you want to associate with the In-Memory DB cluster, specify the following:

1. Number of CPUs (per instance): Increase or decrease the number of CPUs using the slider.

2. RAM Size (per instance): Increase or decrease the size of the RAM using the slider to suit your needs.

Connect the Cluster with a VDC

You can also click Finding Your Private IP Address section on the right side of the window to know how to retrieve a private IP address.

1. Datacenter: The data center is set to Germany/Berlin, by default.

2. Datacenter LAN: Select a LAN from the drop-down list for the data center.

3. Private IP address: Enter the private IP address or subnet using the available Private IPs.

Schedule the Cluster maintenance

Your chosen start time (UTC) plus four hours is the maintenance time.

1. Day: Select a day from the drop-down list to set a day for maintenance.

Define Users

The credentials of any user who has previously been created in the backup will be overwritten.

1. Username: Enter a username to provide access to the In-Memory DB cluster for the respective user.

2. Password: Enter a password for the respective user.

After cluster creation, you can view the list of In-Memory DB clusters, delete them if they are no longer required, or restore a specific cluster backup, if needed.

If you have already defined clusters, the In-Memory DB cluster overview window displays the resources allotted to your contract and the number of used and unused resources.

To view a list of the clusters, follow these steps:

1. Log in to the DCD with your username and password.

2. Go to Menu > Databases > In-Memory DB.

View individual Cluster details and restore a Backup

To view the details of each cluster in the Details window:

1. Log in to the DCD with your username and password.

2. Go to Menu > Databases > In-Memory DB.

3. You can navigate to the Details window using either of these options:

   • Select the name of the cluster.

   • Using the View details option from the OPTIONS column.
4. You can view the following:

   • Properties: Displays the cluster's UUID, DNS name, its version, state, the number of instances created, and the data center location where it is located.

   • Instance configuration: Displays the number of CPU cores utilized and the RAM size used.

   • Maintenance: Displays the stipulated day of the week and the time scheduled for the maintenance window.

   • Estimated price: Displays the cost for the resources used.

   • Backups: Click to display the number of In-Memory DB backups available for restoration. Select Restore to restore a specific backup.

   • Select Restore in the confirmation dialog box.

Quick Links

Endpoint

A regional endpoint is necessary to interact with the In-Memory DB REST API endpoints. For more information, see the API specification file.

Currently, IONOS supports the following endpoints for various locations:

• Berlin, Germany: https://in-memory-db.de-txl.ionos.com/replicasets

• Frankfurt, Germany: https://in-memory-db.de-fra.ionos.com/replicasets

• Logroño, Spain: https://in-memory-db.es-vit.ionos.com/replicasets

• London, Great Britain: https://in-memory-db.gb-lhr.ionos.com/replicasets

• Newark, United States: https://in-memory-db.us-ewr.ionos.com/replicasets

• Las Vegas, United States: https://in-memory-db.us-las.ionos.com/replicasets

• Lenexa, United States: https://in-memory-db.us-mci.ionos.com/replicasets

• Paris, France: https://in-memory-db.fr-par.ionos.com/replicasets

Examples

The documentation contains curl examples, as the tool is available on Windows 10, Linux, and macOS. You can also refer to the following blog posts on the IONOS website that describe how to execute curl in Linux and Windows systems if you encounter any problems.

To delete an In-Memory DB cluster, follow these steps:

1. Log in to the DCD with your username and password.

2. Go to Menu > Databases > In-Memory DB. You will see the list of all In-Memory DB clusters.

3. Click in the OPTIONS column and select Delete.

Alternatively, you can also click on the In-Memory DB cluster that must be deleted and select Delete cluster on the Details window.

1. Select Delete in the dialog box to confirm deletion.

You can retrieve an In-Memory DB instance using its UUID. It is found in the response body when an In-Memory DB instance is created or when you retrieve a list of In-Memory DB instances using GET.

Endpoint

Use a region-specific endpoint from the following list to fetch an instance:

• https://in-memory-db.de-txl.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.de-fra.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.es-vit.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.gb-lhr.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.us-ewr.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.us-las.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.us-mci.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.fr-par.ionos.com/replicasets/{replicasetId}

Request

To query a single instance, you need the id from your create response.

Response

202 Successful operation

You can retrieve a list of In-Memory DB instances. The number of results displayed on each page depends on the limit and offset values. While limit limits the number of response elements, offset specifies the starting point within the collection of resource results returned from the server.

Additionally, you can also use a response filter (filter.name) to list only the In-Memory DB instances that contain the specified displayName.

Endpoint

Use a region-specific endpoint from the following list to retrieve all instances:

• https://in-memory-db.de-txl.ionos.com/replicasets

• https://in-memory-db.de-fra.ionos.com/replicasets

• https://in-memory-db.es-vit.ionos.com/replicasets

• https://in-memory-db.gb-lhr.ionos.com/replicasets

• https://in-memory-db.us-ewr.ionos.com/replicasets

• https://in-memory-db.us-las.ionos.com/replicasets

• https://in-memory-db.us-mci.ionos.com/replicasets

• https://in-memory-db.fr-par.ionos.com/replicasets

Request

Response

202 Successful operation

You can retrieve an In-Memory DB restore using the UUID of its snapshot and restore. It is found in the response body when an In-Memory DB restore is created or when you retrieve a list of In-Memory DB restores using GET.

Endpoint

Use a region-specific endpoint from the following list to retrieve an In-Memory DB restore:

• https://in-memory-db.de-txl.ionos.com/snapshots/{snapshotId}/restores/{restoreId}

• https://in-memory-db.de-fra.ionos.com/snapshots/{snapshotId}/restores/{restoreId}

• https://in-memory-db.es-vit.ionos.com/snapshots/{snapshotId}/restores/{restoreId}

• https://in-memory-db.gb-lhr.ionos.com/snapshots/{snapshotId}/restores/{restoreId}

• https://in-memory-db.us-ewr.ionos.com/snapshots/{snapshotId}/restores/{restoreId}

• https://in-memory-db.us-las.ionos.com/snapshots/{snapshotId}/restores/{restoreId}

• https://in-memory-db.us-mci.ionos.com/snapshots/{snapshotId}/restores/{restoreId}

• https://in-memory-db.fr-par.ionos.com/snapshots/{snapshotId}/restores/{restoreId}

Request

To retrieve a single In-Memory DB restore, you need the id from your create response.

Response

Your values will differ from those in the sample code. It may contain different IDs, timestamps etc.

202 Successful operation

You can retrieve a list of In-Memory DB snapshots. The number of results displayed on each page depends on the limit and offset values. While limit limits the number of response elements, offset specifies the starting point within the collection of resource results returned from the server.

Additionally, you can also use a response filter (filter.name) to list only the In-Memory DB snapshots that contain the specified displayName.

Endpoint

Use a region-specific endpoint from the following list to retrieve all In-Memory DB snapshots:

• https://in-memory-db.de-txl.ionos.com/snapshots

• https://in-memory-db.de-fra.ionos.com/snapshots

• https://in-memory-db.es-vit.ionos.com/snapshots

• https://in-memory-db.gb-lhr.ionos.com/snapshots

• https://in-memory-db.us-ewr.ionos.com/snapshots

• https://in-memory-db.us-las.ionos.com/snapshots

• https://in-memory-db.us-mci.ionos.com/snapshots

• https://in-memory-db.fr-par.ionos.com/snapshots

Request

The following is a sample request:

Response

202 Successful operation

The request creates a new In-Memory DB instance with the ID if the instance does not exist. Otherwise, it updates the existing instance. You can modify an In-Memory DB instance using its UUID found in the response body when an In-Memory DB instance is created or when you retrieve a list of In-Memory DB instances using GET.

Endpoint

Use a region-specific endpoint from the following list to modify an instance:

• https://in-memory-db.de-txl.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.de-fra.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.es-vit.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.gb-lhr.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.us-ewr.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.us-las.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.us-mci.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.fr-par.ionos.com/replicasets/{replicasetId}

Request

To modify a single instance, you need the id from your create response.

Response

Your values will differ from those in the sample code. It may contain different IDs, timestamps etc.

The metadata.state is BUSY when the instance is not yet reachable. This is because the cloud will create a completely new instance and needs to provision new nodes for all the requested replicas. This process runs asynchronously in the background and might take up to 30 minutes.

The metadata state changes to BUSY to enable the creation of a new In-Memory DB instance and provide new nodes for the requested replicas while the cloud remains unreachable. This process runs in the background and may take up to 30 minutes to complete. It works asynchronously, so you do not have to wait until the process is complete.

202 Successful operation

The request creates a new In-Memory DB instance on IONOS DBaaS. Each In-Memory DB instance can contain multiple nodes.

The data center must be provided as a UUID. The easiest way to retrieve the UUID is through the .

Endpoint

Use a region-specific endpoint from the following list to create an In-Memory DB instance:

• https://in-memory-db.de-txl.ionos.com/replicasets

• https://in-memory-db.de-fra.ionos.com/replicasets

• https://in-memory-db.es-vit.ionos.com/replicasets

• https://in-memory-db.gb-lhr.ionos.com/replicasets

• https://in-memory-db.us-ewr.ionos.com/replicasets

• https://in-memory-db.us-las.ionos.com/replicasets

• https://in-memory-db.us-mci.ionos.com/replicasets

• https://in-memory-db.fr-par.ionos.com/replicasets

Request

Response

Your values will differ from those in the sample code. It may contain different IDs, timestamps etc.

You may have noticed that the metadata.state is BUSY and that the instance is not yet reachable. This is because the cloud will create a completely new instance and needs to provision new nodes for all the requested replicas. This process runs asynchronously in the background and might take up to 30 minutes.

202 Successful operation

You can retrieve an In-Memory DB snapshot using its UUID. It is found in the response body when an In-Memory DB instance is created or when you retrieve a list of In-Memory DB snapshots using GET.

Endpoint

Use a region-specific endpoint from the following list to retrieve an In-Memory DB snapshot:

• https://in-memory-db.de-txl.ionos.com/snapshots/{snapshotId}

• https://in-memory-db.de-fra.ionos.com/snapshots/{snapshotId}

• https://in-memory-db.es-vit.ionos.com/snapshots/{snapshotId}

• https://in-memory-db.gb-lhr.ionos.com/snapshots/{snapshotId}

• https://in-memory-db.us-ewr.ionos.com/snapshots/{snapshotId}

• https://in-memory-db.us-las.ionos.com/snapshots/{snapshotId}

• https://in-memory-db.us-mci.ionos.com/snapshots/{snapshotId}

• https://in-memory-db.fr-par.ionos.com/snapshots/{snapshotId}

Request

To retrieve a single snapshot, you need the id from your create response. Remember to update your UUID. The sample UUID in the example is 498ae72f-411f-11eb-9d07-046c59cc737e.

Response

202 Successful operation

You can retrieve a list of In-Memory DB restores. The number of results displayed on each page depends on the limit and offset values. While limit limits the number of response elements, offset specifies the starting point within the collection of resource results returned from the server.

Additionally, you can also use a response filter (filter.name) to list only the In-Memory DB restores that contain the specified displayName.

Endpoint

Use a region-specific endpoint from the following list to retrieve a list of restores:

• https://in-memory-db.de-txl.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.de-fra.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.es-vit.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.gb-lhr.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.us-ewr.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.us-las.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.us-mci.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.fr-par.ionos.com/snapshots/{snapshotId}/restores

Request

Response

Your values will differ from those in the sample code. It may contain different IDs, timestamps etc.

200 Successful operation

The request creates a new restore. You must provide a full restore to create the object.

Endpoint

Use a region-specific endpoint from the following list to create a new restore:

• https://in-memory-db.de-txl.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.de-fra.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.es-vit.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.gb-lhr.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.us-ewr.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.us-las.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.us-mci.ionos.com/snapshots/{snapshotId}/restores

• https://in-memory-db.fr-par.ionos.com/snapshots/{snapshotId}/restores

Request

Response

Your values will differ from those in the sample code. It may contain different IDs, timestamps etc.

202 Successful operation

How can I change my user password?

Unfortunately, updating your password is not currently possible.

What user permissions do I get?

You get access to all command categories, except the commands that are listed in the "dangerous" category. For more information, refer to the .

How do you distinguish between supported and unsupported features?

According to the , stack features that display their logo are not supported.

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

Unfortunately, IONOS 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 .

You can delete an In-Memory DB instance using its UUID. It is found in the response body when an In-Memory DB instance is created or when you a list of In-Memory DB instances.

Endpoint

Use a region-specific endpoint from the following list to delete an instance:

• https://in-memory-db.de-txl.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.de-fra.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.es-vit.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.gb-lhr.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.us-ewr.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.us-las.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.us-mci.ionos.com/replicasets/{replicasetId}

• https://in-memory-db.fr-par.ionos.com/replicasets/{replicasetId}

Request

To delete an In-Memory DB instance, you need the id from your response.

Response

Upon successful deletion, you will receive a 202 Accepted response.