Quotas and limits in Yandex IoT Core
Written by
Updated at July 8, 2024
Yandex IoT Core has the following limits:
- Quotas are organizational restrictions that can be changed by technical support.
- Limits are technical limitations due to Yandex Cloud architectural features. You cannot change the limits.
If you need more resources, you can increase quotas in one of the following ways:
- Generate a request for a quota increase. You must have the
quota-manager.requestOperatorrole or higher, such aseditororadmin. - Contact technical support and tell us which quotas you want increased and by how much.
Quotas
| Type of limit | Value |
|---|---|
| Number of registries per cloud | 10 |
| Number of devices per cloud | 1,000 |
| Number of brokers per cloud | 10 |
| Frequency of sending messages per broker | 50 per second |
| Number of clients concurrently connected to the broker | 50 |
Limits
| Type of limit | Value |
|---|---|
| Maximum size per message | 256 KB |
| Frequency of sending messages per device | No more than once per second |
| Maximum subtopic name length | 1,024 characters |
| Maximum number of aliases per device | 5 |
Note
Message delivery is not guaranteed if the limits are exceeded.
Other restrictions
- The
Retainflag is not supported. When using it, the MQTT broker saves the flagged message and sends it when you subscribe a device or registry to a topic next time. - Persistent sessions, when the MQTT broker saves information about a client (device or registry) to reconnect faster, are not supported.
- The
QoS 2: Exactly oncequality of service level for MQTT is not supported. - There is no guarantee that the devices or registries with the same ClientID cannot connect to the MQTT broker at the same time.