Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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:
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.
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
.
Note:
Remember to update your UUID
. The sample UUID
in the example is 498ae72f-411f-11eb-9d07-046c59cc737e
.
Your instance runs in the default port 6379. For more information, refer to the In-Memory DB documentation.
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}
To query a single instance, you need the id
from your create
response.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
The following path parameter is mandatory:
replicasetId
yes
string
The ID (UUID) of the ReplicaSet. Example: 498ae72f-411f-11eb-9d07-046c59cc737e
.
202 Successful operation
You may ensure the success of creating an In-Memory DB instance by adhering to the following network and resource requirements.
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.
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.
All In-Memory DB instances are backed up automatically. For more information, see Automatic backups.
The request creates a new In-Memory DB instance on IONOS DBaaS. Each In-Memory DB instance can contain multiple nodes.
Note:
Only contract administrators, owners, and users with Access and manage DBaaS privileges can create and manage In-Memory DB instances, provided the new IAM system is disabled.
After creating an instance, you can access it via the corresponding LAN using the same username
and password
specified during creation.
You can only set the username
and password
via the API while creating an In-Memory DB instance. Once configured, they cannot be updated.
The data center must be provided as a UUID
. The easiest way to retrieve the UUID
is through the Cloud API.
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
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
Below is the list of mandatory body parameters:
displayName
string
The human-readable name of your replica set.
In-Memory DB replica set
version
string
The version of your replica set.
7.2
replicas
integer
The total number of replicas in the replica set (one active and n-1 passive).
2
resources
object
The resources of the individual replicas.
"cores": 4
, "ram": 4
persistenceMode
string
Specifies data persistence mode. The values are: None
(default value), AOF
, RDB
, and RDB_AOF
.
RDB
evictionPolicy
string
The eviction policy for the replica set.
The values are: noeviction
, allkeys-lru
, allkeys-lfu
, allkeys-random
, volatile-lru
, volatile-lfu
, volatile-random
, and volatile-ttl
.
connections
object
The network connection for your replica set. Only one connection is allowed.
{ "datacenterId": "5a029f4a-72e5-11ec-90d6-0242ac120003", "lanId": "2", "cidr": "192.168.1.100/24"}
credentials
object
Credentials for the In-Memory DB replicaset.
"username": "DatabaseAdmin"
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
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
.
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}
Note: Remember to update the replicasetId
with a valid UUID
. The sample UUID
in the example is 498ae72f-411f-11eb-9d07-046c59cc737e
.
To modify a single instance, you need the id
from your create
response.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
The following path parameter is mandatory:
replicasetId
yes
string
The ID (UUID) of the ReplicaSet. Example: 498ae72f-411f-11eb-9d07-046c59cc737e
.
Below is the list of mandatory body parameters:
id
string
The ID (UUID) of the ReplicaSet.
1046e9bf-dbc0-5bd3-9291-713d36ab77e9
displayName
string
The human-readable name of your replica set.
In-Memory DB replica set
version
string
The In-Memory DB version of your replica set.
7.2
replicas
integer
The total number of replicas in the replica set (one active and n-1 passive).
2
resources
object
The resources of the individual replicas.
"cores": 4
, "ram": 4
persistenceMode
string
Specifies data persistence mode. The values are: None
(default value), AOF
, RDB
, and RDB_AOF
.
RDB
evictionPolicy
string
The eviction policy for the replica set.
The values are: noeviction
, allkeys-lru
, allkeys-lfu
, allkeys-random
, volatile-lru
, volatile-lfu
, volatile-random
, and volatile-ttl
.
connections
object
The network connection for your replica set. Only one connection is allowed.
{ "datacenterId": "5a029f4a-72e5-11ec-90d6-0242ac120003", "lanId": "2", "cidr": "192.168.1.100/24"}
credentials
object
Credentials for the In-Memory DB replicaset.
"username": "DatabaseAdmin"
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
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
.
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
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
202 Successful operation
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 fetch a list of In-Memory DB instances.
Note: Remember to update your UUID
. The sample UUID
in the example is 498ae72f-411f-11eb-9d07-046c59cc737e
.
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}
To delete an In-Memory DB instance, you need the id
from your create response.
To make authenticated requests to the API, the following fields are mandatory in the request header:
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
The following path parameter is mandatory:
replicasetId
yes
string
The ID (UUID) of the ReplicaSet. Example: 498ae72f-411f-11eb-9d07-046c59cc737e
.
Upon successful deletion, you will receive a 202 Accepted response.
A list of prerequisites to assure success with an In-Memory DB instance creation.
Create an In-Memory DB instance.
Verify the status of an In-Memory DB instance.
Connect to a In-Memory DB instance from your managed Kubernetes cluster.
List all In-Memory DB instances.
Fetch a specific In-Memory DB instance.
Modify a specific In-Memory DB instance.
Delete a specific In-Memory DB instance.
Retrieve a specific In-Memory DB snapshot.
List all In-Memory DB snapshots.
Create an In-Memory DB restore.
Retrieve a specific In-Memory DB restore.
Retrieve a list of In-Memory DB restores.
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
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.
The request creates a new restore. You must provide a full restore to create the object.
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
Note: Remember to replace the snapshotId
with a relevant UUID
.
To make authenticated requests to the API, the following fields are mandatory in the request header:
The following path parameter is mandatory:
Below is the list of mandatory body parameters:
Your values will differ from those in the sample code. It may contain different IDs, timestamps etc.
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
.
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}
Note: Remember to replace the sample values in the request with valid ones.
To retrieve a single In-Memory DB restore, you need the id
from your create
response.
To make authenticated requests to the API, the following fields are mandatory in the request header:
The following path parameter is mandatory:
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
.
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
The following is a sample request:
To make authenticated requests to the API, the following fields are mandatory in the request header:
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
.
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
Note: Remember to replace the snapshotId
with the relevant UUID
. The sample snapshotId
used in the example is a8784665-3d99-5464-af32-30a2967f58e7
.
To make authenticated requests to the API, the following fields are mandatory in the request header:
The following path parameter is mandatory:
Your values will differ from those in the sample code. It may contain different IDs, timestamps etc.
200 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
.
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}
Note: Remember to replace the snapshotId
with a relevant UUID
.
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
.
To make authenticated requests to the API, the following fields are mandatory in the request header:
The following path parameter is mandatory:
202 Successful operation
This topic describes connecting to the In-Memory DB instance from your managed Kubernetes cluster.
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
.
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:
Connect node pools to the private LAN, which is connected to the database:
Note: It may take a while for the node pool to be ready.
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.
Alternatively, you can also use the following commands:
Create the pod using either of these commands: kubectl run redis-client --rm -it --image=redis -- /bin/bash
or kubectl apply -f pod.yaml
Attach the pod and test connectivity:
Prerequisites:
— Ensure that the connectivity-test
pod already exists and that the node pool on which it is running has the same private LAN attached as the In-Memory DB instance.
— To establish a secure connection via the TLS, the --tls
and --cacert
command line options must be passed to the redis-cli
.
Result: The database starts accepting connections.
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
snapshotId
yes
string
The ID (UUID) of the Snapshot. Example: a8784665-3d99-5464-af32-30a2967f58e7
.
replicasetId
string
The ID of the replica set the restore was applied on.
ac71d588-f2bb-481c-8905-52d37b5cb3b4
.
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
snapshotId
yes
string
The ID (UUID) of the snapshot. Example: a8784665-3d99-5464-af32-30a2967f58e7
.
restoreId
yes
string
The ID (UUID) of the restore. Example: 39fe1580-552b-5182-8939-a3ac6c38f94c
.
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
snapshotId
yes
string
The ID (UUID) of the snapshot. Example: a8784665-3d99-5464-af32-30a2967f58e7
.
Authorization
yes
string
Provide a header value as Bearer
followed by your token
.
Content-Type
yes
string
Set this to application/json
.
snapshotId
yes
string
The ID (UUID) of the snapshot. Example: 498ae72f-411f-11eb-9d07-046c59cc737e
.