Quotas and limits in Yandex IoT Core
Written by
Yandex IoT Core has the following limits:
- Quotas are organizational restrictions that can be changed by technical support on request.
- Limits are technical limitations due to Yandex Cloud architectural features. The limits cannot be changed.
Quotas
| Type of limit | Value |
|---|---|
| Number of registries per cloud | 10 |
| Number of devices per cloud | 1000 |
| 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 length of the subtopic name | 1024 symbols |
| 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 the next time you subscribe a device or registry to a topic. - Persistent Sessions, when the MQTT broker saves information about a client (device or registry) to reconnect faster, aren't supported.
- The
QoS 2: Exactly oncequality of service level for MQTT is not supported. - There is no guarantee that devices or registries with the same ClientID cannot connect to the MQTT broker at the same time.