Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for MongoDB
  • Getting started
    • Resource relationships
    • Network in Yandex Managed Service for MongoDB
    • Quotas and limits
    • Storage in Yandex Managed Service for MongoDB
    • Backups
    • Replication and fault tolerance
    • Sharding
    • Users and roles
    • Maintenance
    • Supported clients
    • MongoDB settings
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  1. Concepts
  2. Quotas and limits

Managed Service for MongoDB quotas and limits

Written by
Yandex Cloud
Improved by
amatol
Updated at April 28, 2025

Managed Service for MongoDB has the following limits:

  • Quotas are organizational constraints that our support team can change upon request.
  • Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.

If you need more resources, you can increase your quotas in one of the following ways:

  • Make a request to increase your quotas.
  • Contact support, detailing which quotas you want increased and by how much.

To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g.,editor or admin.

You can manage quotas using Cloud Quota Manager.

QuotasQuotas

Type of limit Value
Number of clusters per cloud 16
Total number of processor cores for all database hosts per cloud 96
Total virtual memory for all database hosts per cloud 640 GB
Total storage capacity for all clusters per cloud 4,096 GB

LimitsLimits

Type of limit Minimum value Maximum value
Host class b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM)
Number of shards per cluster 1 10
Number of hosts per shard when using an HDD or SSD network storage or an ultra high-speed network storage with three replicas (SSD) 1 7
Number of hosts in a shard when storing data on non-replicated or local SSDs* 3 7
Number of hosts per cluster 1 or 3 hosts depending on the disk type; the cluster is created in an unsharded state. 70 (10 shards, 7 hosts)
Amount of data on the host when using network HDD or SSD storage 10 GB 2048 GB
Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) 93 GB 2,232 GB
Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake)* 100 GB 1,500 GB
Amount of data per host when using local SSD storage (for Intel Ice Lake)* 368 GB 2944 GB
Number of databases per cluster 1 1000

* Read more on how platform selection affects available storage types.

The maximum available number of simultaneous connections to a single Managed Service for MongoDB cluster host depends on the amount of RAM on the host:

Amount of RAM Maximum number of connections
2 GB 2048
4 GB 4096
8 GB 8192
16 GB or higher 16 384

Was the article helpful?

Previous
Network in Yandex Managed Service for MongoDB
Next
Storage in Yandex Managed Service for MongoDB
© 2025 Direct Cursus Technology L.L.C.