Creating a MongoDB Database
This page covers the configuration specific to MongoDB — its Database Mode and any engine-specific settings shown below. The rest of the creation flow — opening the wizard, namespace and name, version, machine profile, storage, and optional features — is the same for every engine and is documented in Common Steps.
Database Mode
Select the topology under Database Mode. Three modes are available:
- Standalone — A single-node database without high availability or sharding. Best for development or low-traffic workloads.
- Replicated Cluster — A MongoDB ReplicaSet for high availability.
- Sharded Cluster — A fully sharded MongoDB cluster for high performance and high availability.
Replicated Cluster
When Replicated Cluster is selected, two additional fields appear:
| Field | Description |
|---|---|
| Replicaset Name | The name for the replica set (e.g., rs0). Required. |
| Replicaset Number | The number of replica members (e.g., 3). Required. |
| mongodb+srv style DNS | Toggle on to enable mongodb+srv connection string support for this replica set. |
Sharded Cluster
When Sharded Cluster is selected, three subsections appear — Shard Nodes, Config Server, and Mongos — each configurable independently.
Shard Nodes — Configure how MongoDB data is partitioned, replicated, and resourced across your cluster.
| Field | Description |
|---|---|
| Shards | Number of shard partitions (e.g., 2). Required. |
| Replicaset Number | Number of replicas per shard (e.g., 3). Required. |
| Storage size | Disk size per shard node (e.g., 2Gi). Required. |
| Machine | Preset machine profile or custom for manual CPU/memory. |
| CPU | CPU request per shard node (e.g., 900m). |
| Memory | Memory request per shard node (e.g., 1Gi). |
Config Server — Stores metadata about the sharded cluster including chunk distribution and shard configuration. Must run as a replica set.
| Field | Description |
|---|---|
| Replicaset Number | Number of config server replicas (e.g., 3). Required. |
| Storage size | Disk size per config server node (e.g., 2Gi). Required. |
| Machine | Preset machine profile or custom. |
| CPU | CPU request (e.g., 800m). |
| Memory | Memory request (e.g., 1Gi). |
Mongos — Acts as the query router for the sharded cluster, directing client requests to the appropriate shards based on metadata from Config Servers.
| Field | Description |
|---|---|
| Replicaset number | Number of Mongos router instances (e.g., 2). Required. |
| Machine | Preset machine profile or custom. |
| CPU | CPU request (e.g., 500m). |
| Memory | Memory request (e.g., 1Gi). |
Additional MongoDB Options
| Field | Description |
|---|---|
| Arbiter | Toggle on to add an arbiter member (votes in elections but stores no data). Configure its pod resources. |
| Hidden Node | Toggle on to add hidden replica members (replicate data but are invisible to clients). Set Replicas, resources, and storage. |
| HostName / IP | Optional host name and IP used to build the connection string and certificate SANs. |
Create a MongoDB Database
- Open the wizard and select MongoDB — see Getting Started and Select a Database Type.
- Set the namespace and name.
- Pick the database version and the Database Mode described above, then set the machine profile and storage — see Configure the Database.
- Optionally configure Advanced Configuration (labels, deletion policy, credentials, point-in-time recovery) and Additional Options (monitoring, backup, TLS, gateway).
- Click Deploy.