IONOS MongoDB API allows you to create a MongoDB cluster.
In the following examples, we assume that you want to use the data center UUID b1432c51-c20a-4f83-876f-c3a8a9e1fbec
.
To list the available sizing templates using the API:
Request
Response
Choose the sizing that fits your use case and specify it on cluster creation. For more information about how to calculate resource usage, see Sizing.
Currently, we do not support changing instance sizes for single instance clusters. You would need to create a new cluster for this.
For the following examples, we assume that you want to create a small test cluster and therefore chose the template 15c6dd2f-02d2-4987-b439-9a58dd59ecc3
.
CPU, RAM, storage, and storage type are provided and not limited by a set of predefined templates as in the business edition.
CPU, RAM, storage, and the number of database clusters are counted against quotas. For more information about how to calculate resource usage, see Sizing.
Currently, we don't support changing the cluster storage size for single instance clusters. You would need to create a new cluster to change the cluster storage size.
Database performance depends on the storage type ( HDD
, SSD
and SSD Premium
). Choose the storage type that is suitable for your workload.
Currently, the database cluster does not have automatic IP address management, and the only supported subnet is /24. To create a MongoDB cluster, specify as many free IP addresses as the number of instances in your cluster. Make sure that the IP addresses are not used by other servers in your LAN. You can choose the IP address by using one of the following methods:
You can choose the IP addresses of the subnet assigned to you by IONOS if you rely on IONOS-provided DHCP. The Network Interface Card (NIC) configuration contains information about the subnet. To prevent a collision with the DHCP IP range, choose an IP address between x.x.x.3/24
and x.x.x.10/24
. The IONOS DHCP never assigns IP addresses in that range.
If you run your own DHCP, select IP addresses that cannot be assigned by your DHCP server.
If you assign IP addresses manually, you may use any IP addresses in that subnet and need to make sure that it is not used anywhere else.
For example, assume your private LAN uses the IP range 10.1.1.0/24
and you want a cluster with three instances. Then, you could provide us with the IP addresses 10.1.1.3/24
, 10.1.1.4/24
and 10.1.1.5/24
. Note that the prefix length (/24
) still is the same as for the whole subnet. We only use the single IPs that you specify, but we need the prefix length to configure routing correctly.
Warning: You cannot delete a LAN while a database cluster is still attached. If you want to delete the LAN, then first delete the database cluster.
This request creates a database cluster with three instances of MongoDB version 5.0.
Note: Only contract administrators and owners can create and change database clusters. In contrast, the running database cluster can be accessed from all servers in the specified LAN.
Request
Response
Note: We will use 498ae72f-411f-11eb-9d07-046c59cc737e as example for the cluster ID in following examples.
At this point, you have created your first MongoDB cluster. The deployment of the database takes several minutes. To determine when your cluster is ready, see Querying database status.
This request will create a database cluster with three instances of MongoDB version 6.0.
Note: The use of these enterprise attributes. edition
specifies an enterprise edition. cores
specifies the number of CPUs. ram
specifies the RAM amount in MB. storageSize
specifies the storage amount in MB. storageType
specifies the storage type. The possible values are HDD
, SSD Standard
, and SSD Premium
Note: Only contract administrators and owners can create and change database clusters. However, the running database cluster can be accessed from all servers in the specified LAN.
Request
Response
Note: In the following examples, we use 498ae72f-411f-11eb-9d07-046c59cc737e as the cluster ID.
At this point, you have created your first MongoDB cluster. The deployment of the database takes several minutes. To determine when your cluster is ready, see Querying database status.
You may have noticed that the state
is BUSY
and that the database cluster is unreachable. This is because the cloud creates a completely new cluster and needs to provision new instances. This process runs asynchronously in the background and might take several minutes.
You can poll the API to see when the state
switches to AVAILABLE
and health
to HEALTHY
meaning a fully functional cluster.
To query a single cluster, you require the id
from your "create" response.
If you do not know your MongoDB cluster-ID, you can also list all clusters and look for the one for which to query the status.
Now that the cluster is available, you can connect to your MongoDB cluster using the mongo shell tool and the connection string from the API response and should see the mongo shell prompt:
Reminder: The connection must be performed from an extra VM.
Connecting to a MongoDB cluster doesn't require authentication. However, nearly all other operations with a cluster require authentication. For example, when you try to list all databases:
You cannot create or modify users from within MongoDB itself. The user management for IONOS MongoDB clusters happens completely via the IONOS API. You can read more about this in the documentation on Users Management.
Assume you have created a user jdoeionos
on database example
with the role readWrite
on example
. Then you can authenticate like this: and can afterward write and read data:
Result: You now have a ready-to-use MongoDB cluster.