MongoDB - Capabilities and Limitations

Find out what are the capabilities and limitations of the Public Cloud Databases for MongoDB offer

Last updated September 27th, 2021


This page provides the technical capabilities and limitations of the Public Cloud Databases for MongoDB offer.

Capabilities and limitations

Supported regions

The Public Cloud Databases offer is available in the following regions:

  • BHS (Beauharnois, Canada)
  • DE (Frankfurt, Germany)
  • GRA (Gravelines, France)
  • UK (London, United Kingdom)
  • WAW (Warsaw, Poland)

MongoDB versions

The Public Cloud Databases offer supports the following MongoDB versions:

  • MongoDB 4.2
  • MongoDB 4.4

MongoDB recommends always installing and using the latest stable version of MongoDB. See MongoDB Versioning for more information.

MongoDB Drivers

You can use anyone of the MongoDB-recommended driver to access your cluster.


Three plans are available:

  • Essential
  • Business
  • Enterprise (coming soon - stay tuned!)

Here is an overview of the various plans capabilities:

Plan Number of nodes MongoDB License Network BI Connector Compass
Essential 1 Community Public only Not available Available
Business 3 to 8 Community Public and Private (vRack) Not available Available
Enterprise 3 to 8 Enterprise Public and Private (vRack) Available Available

Your choice of plan affects the number of nodes your cluster can run as well as the MongoDB license type.


  • Essential: The cluster supports at most one node.
  • Business or Enterprise: The cluster can support 3 to 8 nodes.

License type

  • Essential and Business plans use the MongoDB Community license.
  • Enterprise plans upgrade your cluster so that it uses the MongoDB Enterprise license, giving you the capability to use the MongoDB BI Connector as well as MongoDB Compass.

License cost is included inside the service plans. You cannot bring your own licenses.

Hardware resources

Here are the node types you can choose from:

Name Disk (GB) Cores Memory (GB)
db1-7 50 2 7
db1-15 100 4 15
db1-30 200 8 30
db1-60 400 16 60
db1-120 400 32 120

Right now, all nodes of a given cluster should be of the same type and live in the same regions.

Effective storage

The disk size listed above is the total disk size of the underlying machine, however, a small part of it goes towards the OS install.

We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore, The customer will :

  1. receive a first email alert once cluster is reaching 80% storage capacity;
  2. receive a second email alert once cluster is reaching 90% storage capacity;
  3. have his database instance moved in "read-only" mode, meaning no more writes can be done.



MongoDB clusters are reachable through default port 27017.

Public networking can be used for all the offers.

Private Networking (vRack) is available for Business and Enterprise.

When using private networking, some network ports get created in the private network of your choice. Thus, further operations on that network might suffer from some restrictions - e.g. you won't be able to delete the network if you didn't stop the Public Cloud Databases services first.

Ingress and Egress traffic are included in the service plans and unmetered.


Essential plan clusters are automatically backed up daily during their maintenance window. Backup retention is 1 day.

Business plan clusters are automatically backed up daily during their maintenance window. Backup retention is 7 days.

Enterprise plan clusters are automatically backed up daily during their maintenance window, with PITR support. Backup retention is 30 days.

Logs and Metrics

Logs and metrics are available via the OVHcloud Public Cloud Control Panel. As of today, you can't export Logs and metrics, neither plug them to a remote tool.

Logs retention : 1000 lines of logs; Metrics retention : 1 calendar year.

Please note that if the database instance is deleted, logs and metrics are also automatically deleted.

Users and roles

Creation of users is allowed with the proposed roles :

  • readAnyDatabase
  • readWriteAnyDatabase
  • userAdminAnyDatabase
  • dbAdminAnyDatabase

In order to properly manage your MongoDB cluster, some MongoDB users are set up in your clusters by OVHcloud:

  • admin@admin is your initial user
  • mms-automation@admin is a technical user required for automation purposes
  • backup-*@admin are used to perform backups

Furthermore, user creation from the MongoDB Shell is not supported: You need to use the OVHcloud API or the OVHcloud Control Panel in order to manage your clusters' users. Any user created through the mongo shell will be deleted by the automation mechanism.

We want your feedback!

We would love to help answer questions and appreciate any feedback you may have. Join our community of users on

Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service!

Did you find this guide useful?

Please feel free to give any suggestions in order to improve this documentation.

Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.

Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.

Thank you. Your feedback has been received.

These guides might also interest you...

OVHcloud Community

Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.

Discuss with the OVHcloud community