MongoDB® - Capabilities and limitations

Learn about the technical capabilities and limitations of the Cloud Databases for MongoDB® offer.

 

Capabilities and limitations

Supported regions

To view Cloud Databases' availability, please see our regions and availability webpage.

Entire database instances have to be in the same region.

 

MongoDB® versions

The Cloud Databases offer supports the following MongoDB® versions:

• MongoDB® 5.0
• MongoDB® 6.0
• MongoDB® 7.0
• MongoDB® 8.0

Please refer to the Lifecycle policy 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

The available plans are:

• Discovery: 3 nodes
• Production: 3 nodes

 

License type

All plans use the MongoDB® Community license.

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

 

Hardware resources

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

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

 

Features

Network

MongoDB® clusters are reachable through the 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 are 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 a 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.
• 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.
• OpenStack subnet routes announcement will not be applied to your services.
• You can only create private network services if you are the original owner of the network. You cannot create private network services on a shared network.

 

Authorized IPs

Once your service is up and running, you can 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.

See the Automated backups guide for more information.

 

Logs and Metrics

Logs and metrics are available via the OVHcloud Control Panel, API, and can be forwarded to Logs Data Platform. For more information about logs forwarding, see our Set up logs forwarding guide.

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

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:

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 is 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 to manage your clusters' users. Any user created through the Mongo shell will be deleted by the automation mechanism.

 

Data encryption

For detailed information about encryption, see our Security Overview guide.

 

Go further

Browse all the Databases guides.

Browse the rest of the OVHcloud US documentation for guides on our other products and services.

Learn more about Managed Databases on the OVHcloud US website.

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.

OVHcloud Managed Databases and Analytics:

• Grafana® is a registered trademark of Grafana Labs and is used with the permission of Grafana Labs. OVH SAS and its subsidiaries are not affiliated with or endorsed by Grafana Labs.
• Kafka® is a registered trademark of The Apache Software Foundation and has been licensed for use by OVHcloud, who has no affiliation with and is not endorsed by The Apache Software Foundation.
• MongoDB® is a registered trademark of MongoDB, Inc.
• MySQL® is a registered trademark of Oracle and/or its affiliates.
• PostgreSQL® is a registered trademark of the PostgreSQL Community Association of Canada.