You can add a MongoDB cluster on any of the following editions: Playground, Business, or Enterprise.
Prerequisites: Before setting up a database, make sure you are working within a provisioned VDC that contains at least one virtual machine (VM) from which to access the database. The VM you create is counted against the quota allocated in your contract. For more information on databases quota, see Resource Allocation.
Note: Database Manager is available for contract administrators, owners, and users with Access and manage DBaaS privileges only. You can set the privilege via the DCD group privileges.
To create a MongoDB cluster, follow these steps:
1. In the DCD, click Menu > Databases > MongoDB.
Info: The Resource allocation section displays the resources allotted to your contract and the number of used and unused resources if you have already created MongoDB clusters.
2. In the MongoDB cluster overview window, click Create cluster to create a new MongoDB cluster.
3. Specify the following in the Properties section:
Provide an appropriate Cluster Name.
From the drop-down list, choose a Location where your data for the database cluster can be stored. You can select an available data center within the cluster's data directory to create your cluster.
Select the appropriate MongoDB Version. The IONOS Database Manager supports MongoDB versions 5.0 and 6.0.
4. Choose an Edition.
In the Playground edition, the following standard resources are available:
RAM Size (GB): 2.
vCPU: 1.
Storage Size: 50 GB.
Note: You can create one playground instance for free and test MongoDB. For every additional instance that you create apart from the first instance, the charges are applicable accordingly.
In the Business edition, select a relevant Template to based on the resources required for creating your MongoDB cluster. The resources vary for each of the predefined templates based on the RAM Size (GB), vCPU, and Storage Size. Select a template from the drop-down list that suits your needs.
Note: Depending on the resource limit allocation as per your contract, some of the templates may not be available for selection.
In the Enterprise edition, choose the following resources for creating each node of your MongoDB cluster. The total billed resources will be these values multiplied by the number of instances and the number of shards (if applicable).
Upon selecting Enterprise edition, you can choose from the following in the Resources section:
Number of CPUs (per instance): You can choose between 1 and 31 CPU cores using the slider or choose from the available shortcut values.
RAM Size (per instance): Values of up to 230 GB RAM sizes are possible. Select the RAM size using the slider or choose from the available shortcut values.
Storage Type: The SSD Premium, SSD Standard, or HDD storage options are available.
Storage Size: Set the storage size value to at least 100 GB in case of SSD Standard and Premium storage types for optimal performance of the database cluster. You can configure the storage size to a maximum of 4 TB.
5. Configure your cluster in the Cluster configuration section.
Database type: It is set to Replica Set, by default. This database type maintains replicas of data sets and offers redundancy and high data availability.
Note: The Sharded Cluster database type is not available for selection in the Playground edition.
Instances: By default, one instance is offered for free in this edition to host a logical database manager environment to catalog your databases.
Database type: It is set to Replica Set, by default. This database type maintains replicas of data sets and offers redundancy and high data availability.
Note: The Sharded Cluster database type is not available for selection in the Business edition.
Instances: Select a value from the drop-down list to host a logical database manager environment to catalog your databases. By default, one instance and three instances are possible in the Business edition.
Database type: Select the Database type from the following:
Replica Set: Maintains replicas of datasets; offers redundancy and high availability of data.
Sharded Cluster: Maintains collection of datasets that are distributed across many shards (servers) and hence offers horizontal scalability.
Note: For sharded clusters, an additional three config server instances are created with sizing of two cores, 4 GB of memory, and 40 GB of storage each. These instances are excluded from the billed resources.
Amount of shards: Define the Amount of shards between two to a maximum of thirty-two shards. This is applicable to Sharded Cluster only.
Instances: Select the number of instances to host a logical database manager environment to catalog your databases. By default, three instances are possible in the Enterprise edition.
Backup Location: Select a backup location that is explicitly the location of your backup (region). You can have off-site backups by using a region that is not included in your database region.
BI Connector enabled: Toggle to enable the MongoDB Connector for Business Intelligence (BI) to query a MongoDB database by using SQL commands to aid in the data analysis. If you do not want to use BI Connector, you can toggle off this setting.
6. In the Network configuration section, set up the following:
Datacenter: Select a data center from the available drop-down list.
Datacenter LAN: Select a LAN for the chosen data center.
IP/Subnet: Enter the private IP or subnet address in the correct format by using the available Private IPs. For Business and Enterprise editions, specify one private IP/Subnet address detail for every instance based on the chosen number of Instances.
Note: To know your private IP address/Subnet, you need to:
Create a single server connected to an empty private LAN and check the IP assigned to that NIC in that LAN. The DHCP in that LAN is always using a /24 subnet, so you have to reuse the first 3 octets to reach your database.
To prevent a collision with the DHCP IP range, it is recommended to use IP addresses ending between x.x.x.3/24 and x.x.x.10/24 (which are never assigned by DHCP).
If you have disabled DHCP on your private LAN, then you need to discover the IP address on your own.
7. In the Maintenance period (optional) section, set the following:
Day: From the drop-down list, choose the preferred day on which the maintenance of the cluster must take place.
Start Time (UTC): Set the time (in UTC) for the maintenance of the MongoDB cluster. Use the pre-defined format (hh:mm:ss) or you can use the clock. The maintenance occurs in a 4-hour-long window.
8. Click Save to provision the creation of the MongoDB cluster.
Note: The Estimated price will be displayed based on the input. The estimated cost is exclusive, where certain variables like traffic and backup are not considered.
Result: The MongoDB cluster with the chosen edition is created.
