Capabilities and Limitations of Public Cloud Databases for MongoDB

Objective

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)
• SBG (Strasbourg, France)
• SGP (Singapore, Singapore)
• EU-WEST-PAR (Paris, France)
• EU-SOUTH-MIL (Milan, France)
• UK (London, United Kingdom)
• WAW (Warsaw, Poland)
• RBX (Roubaix, France)
• AP-SOUTH-MUM (Mumbai, India)

MongoDB versions

The Public Cloud Databases offer supports the following MongoDB versions:

• MongoDB 6.0
• MongoDB 7.0
• MongoDB 8.0

Please refer to the DBMS lifecycle policy guide for recommendations on version upgrades and end of life announcements of major versions. Additionally, MongoDB recommends always installing and using the latest stable version of MongoDB. See MongoDB Versioning for more information.

MongoDB Drivers

MongoDB drivers provide the interface for applications to interact with MongoDB databases. They offer:

• Native Language Support: Drivers are available for various programming languages, including JavaScript (Node.js), Python, Java, C#, PHP, Ruby, Go, and more.
• Asynchronous Operations: Many drivers support non-blocking, asynchronous operations to improve performance.
• Comprehensive Documentation: Detailed guides and examples to help developers implement database operations.
• Compatibility: Drivers are designed to work seamlessly with MongoDB features, ensuring reliable and efficient data manipulation.

These drivers ensure that applications can efficiently and securely communicate with MongoDB databases across different programming environments.

Plans

Here is an overview of the capabilities of the three plans available:

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

Nodes

• Discovery: The cluster contains 3 nodes.
• Production and Advanced: The cluster can support 3 to 8 nodes including optionally an analytics node.

License type

• Discovery, and Production plans use the MongoDB Community license.
• Advanced plan upgrades your cluster so that it uses the MongoDB Enterprise license.

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

Hardware resources

Please refer to the price page for details on node types and their specifications.

Features

Network

MongoDB clusters are reachable through default port 27017.

Public as well as private networking (vRack) can be used for all the offers. Private network is not available for the Discovery offer.

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

The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.

Private network considerations

Here are some considerations to take into account when using private network:

• Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
• DHCP must be enabled in your private network in order to launch MongoDB clusters in the said private network.
• When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
• Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
• You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.

Authorised IPs

Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorize incoming traffic. Until then, your service will be unreachable.

Backups

Discovery plan clusters are not backed up.

Production plan clusters are automatically backed up daily. Backup retention is 7 days.

Advanced plan clusters are automatically backed up daily, with PITR support. Backup retention is 30 days with PITR capability for the last 24 hours.

See the Automated Backups guide for more information.

Logs and Metrics

Logs and metrics are available through the Control Panel, API, and can be forwarded to Logs Data Platform. See the Public Cloud Databases - How to setup logs forwarding guide for more information.

• 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:

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.

If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.

Join our community of users.

Are you on Discord? Connect to our channel at https://discord.gg/ovhcloud and interact directly with the team that builds our databases service!