Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Managed Service for PostgreSQL
  • Getting started
    • Resource relationships
    • Planning a cluster topology
    • High availability clusters
    • Networking in Managed Service for PostgreSQL
    • Quotas and limits
    • Storage in Managed Service for PostgreSQL
    • Backups
    • Assigning roles
    • Managing connections
    • Replication
    • Maintenance
    • Supported clients
    • PostgreSQL settings
    • Indexes
    • SQL command limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  1. Concepts
  2. Quotas and limits

Quotas and limits in Managed Service for PostgreSQL

Written by
Yandex Cloud
Improved by
amatol
Updated at December 25, 2025

Managed Service for PostgreSQL has the following limits:

  • Quotas are organizational constraints that can be changed by support on 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 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 your quotas with Cloud Quota Manager.

QuotasQuotas

Type of limit

Value

Number of clusters per cloud
mdb.clusters.count

16

Total number of CPU cores for all database hosts in a single cloud
mdb.cpu.count

64

Total amount of virtual memory for all database hosts in a single cloud
mdb.memory.size

512 GB

Total storage capacity for all clusters in a single cloud
mdb.ssd.size

4,096 GB

Number of GPUs
mdb.gpu.count

0

LimitsLimits

Type of limit Minimum value Maximum value
Host class b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) m4a-c224-m1792 (224 vCPU AMD Zen 4, 1,792 GB RAM)
Number of hosts per cluster configured with either HDD/SSD network storage or an ultra-fast triple-replicated SSD network storage 1 16
Number of hosts per cluster configured with either non-replicated or local SSD storage 3 16
Data volume per host with SSD network storage 10 GB 4,096 GB
Data volume per host with HDD network storage 10 GB 2,048 GB
Data volume per host with either non-replicated SSD storage or ultra-fast triple-replicated SSD network storage 93 GB 10,230 GB
Data volume per host with SSD local storage (for Intel Broadwell and Intel Cascade Lake platforms) 100 GB 1,500 GB
Data volume per host with SSD local storage (for Intel Ice Lake platform) 368 GB 5888 GB
Connections per user 1 15,985
Number of databases per cluster 1 1000

Was the article helpful?

Previous
Networking in Managed Service for PostgreSQL
Next
Storage in Managed Service for PostgreSQL
© 2026 Direct Cursus Technology L.L.C.