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

Quotas and limits in Yandex Managed Service for Valkey™

Written by
Yandex Cloud
Updated at June 20, 2025

Yandex Managed Service for Valkey™ has the following limits:

  • Quotas are organizational constraints that can be changed by support on request.
  • Limits are technical constraints due to 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 and specify 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 with Cloud Quota Manager.

QuotasQuotas

Type of limit

Value

Number of clusters per cloud
mdb.clusters.count

16

Total number of processor cores for all database hosts per cloud
mdb.cpu.count

64

Total virtual memory for all database hosts per cloud
mdb.memory.size

512 GB

Total storage capacity for all clusters per cloud
mdb.ssd.size

4,096 GB

LimitsLimits

Type of limit Minimum value Maximum value
Host class b2.medium (burstable, 4 GB RAM) hm3-c20-m320 (20 vCPUs, Intel Ice Lake, 320 GB RAM)
Number of hosts per unsharded cluster 1 or 3 depending on the disk type 7
Number of shards in a sharded 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 per shard when using local SSD storage* 2 7
Number of hosts per shard when using non-replicated SSD storage* 3 7
Number of hosts per sharded cluster 1, 2, or 3 hosts depending on the disk type 70 (10 shards, 7 hosts)
Amount of data per host when using network SSD storage Twice the selected amount of RAM 4,096 GB
Amount of data per host when using a non-replicated SSD storage* or an ultra high-speed network storage with three replicas (SSD) Twice the selected amount of RAM but at least 93 GB 8,184 GB
Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake)* Twice the selected amount of RAM but at least 100 GB 1,500 GB
Amount of data per host when using local SSD storage (for Intel Ice Lake)* Twice the selected amount of RAM but at least 368 GB 2944 GB
Number of cluster connections — 65 000

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

Was the article helpful?

Previous
Available commands
Next
Disk types
© 2025 Direct Cursus Technology L.L.C.