Quotas and limits in Managed Service for Apache Kafka®
Written by
Updated at November 24, 2025
Managed Service for Apache Kafka® 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.
Quotas
|
Type of limit |
Value |
|
Number of clusters per cloud |
16 |
|
Total number of processor cores for all database hosts per cloud |
64 |
|
Total virtual memory for all database hosts per cloud |
512 GB |
|
Total storage capacity for all clusters per cloud |
4,096 GB |
|
Number of GPUs |
0 |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b2.medium (2 × 50% vCPU Intel Cascade Lake, 4 GB RAM) | m4a-c224-m1792 (224 vCPU AMD Zen 4, 1,792 GB RAM) |
| Number of brokers per cluster when using an HDD or SSD network storage, or an ultra high-speed network storage with three replicas (SSD) | 1 | 32 |
| Number of brokers in a cluster when using non-replicated or local SSDs | 1 | 32 |
| Amount of data on the broker when using SSD network storage | 10 GB | 32,768 GB |
| Amount of data on the broker when using HDD network storage | 10 GB | 2,048 GB |
| Amount of data per broker when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) | 93 GB | 8,184 GB |
| Amount of data on the broker when using local SSD storage (for Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data on the broker when using local SSD storage (for Intel Ice Lake) | 368 GB | 5888 GB |