Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Blog
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
Yandex project
© 2023 Yandex.Cloud LLC
Trial period
  • How to use the free trial
  • Grant terms of use
  • Trial period restrictions
  • Monitoring resource usage
  • End of trial period
  • Upgrading to the paid version
  1. Trial period restrictions

Trial period restrictions

Written by
Yandex Cloud
,
improved by
amatol
  • Service Level Agreement (SLA)
  • Support
  • Yandex Cloud Marketplace
  • Service quotas and limits
    • Yandex Compute Cloud
    • Yandex Object Storage
    • Yandex Virtual Private Cloud
    • Yandex Resource Manager
    • Yandex Network Load Balancer
    • Yandex Managed Service for ClickHouse
    • Yandex Managed Service for MongoDB
    • Yandex Managed Service for MySQL
    • Yandex Managed Service for PostgreSQL
    • Yandex Managed Service for Redis
    • Yandex Message Queue
    • Yandex SpeechKit
    • Yandex Translate
    • Yandex Vision

The free trial is intended for testing and exploring the features of the cloud infrastructure. During the trial period, you can use Yandex Cloud resources with some restrictions.

Service Level Agreement (SLA)

The SLA doesn't apply to the trial period. We don't recommend running production applications in Yandex Cloud during the trial period.

Support

Technical support is provided in full during the trial period. For more information, see Requesting technical support.

Yandex Cloud Marketplace

The following products are not available during the trial period:

  • Microsoft SQL Server
  • Windows Server Standard
  • Windows RDS

Service quotas and 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 and limits for Yandex Cloud services during the trial period are listed below.

Yandex Compute Cloud

Quotas

Type of limit Value
Number of virtual machines per cloud 12
Total number of vCPUs for all VMs per cloud 32
Total virtual memory for all VMs per cloud 128 GB
Total number of disks per cloud 32
Total HDD storage capacity per cloud 500 GB
Total SSD storage capacity per cloud 200 GB
Total SSD storage capacity per cloud 558 GB
Number of non-replicated disk placement groups per cloud 5
Total number of disk snapshots per cloud 32
Total storage capacity of all disk snapshots per cloud 400 GB
The number of disk snapshot schedules in one cloud 32
Total number of file stores per cloud1 100
Total HDD file storage capacity per cloud1 0 B
Total SDD file storage capacity per cloud1 0 B
Number of images per cloud 8
Number of images optimized for deployment per cloud1 0
Number of instance groups per cloud 10
The number of GPUs for all VMs per cloud1 0
Number of concurrent operations per folder 15
Maximum number of placement groups per cloud 2
Number of dedicated hosts per dedicated host group1 0
Number of dedicated host groups per cloud 0

1 To increase quotas for file storage, virtual machines with GPUs, deployment-optimized images, or dedicated hosts, please contact technical support.

VM limits

Limits per virtual machine depend on the virtual machine platform:

Intel Broadwell
Intel Cascade Lake
Intel Ice Lake
Type of limit Value
Maximum number of vCPUs per VM 32
Maximum virtual memory per VM Without GPU: 256 GB
With GPU: 384 GB
Maximum number of disks and file stores attached to a single VM2 Less than 18 vCPUs: 8
From 18 vCPUs: 163
Maximum number of GPUs connected to a single VM 4
Maximum number of security groups per interface 5
Maximum number of VMs in a single placement group 5
Type of limit Value
Maximum number of vCPUs per VM Without GPU: 80
With GPU: 64
Maximum virtual memory per VM Without GPU: 1280 GB
With GPU: 384 GB
Maximum number of disks and file stores attached to a single VM2 Less than 20 vCPUs: 8
From 20 vCPUs: 163
Maximum number of GPUs connected to a single VM 8
Maximum number of security groups per interface 5
Maximum number of VMs in a single placement group 5
Type of limit Value
Maximum number of vCPUs per VM 96
Maximum virtual memory per VM 640 GB
Maximum number of disks and file stores attached to a single VM2 Less than or equal to 32 vCPUs: 8
More than 32 vCPUs: 163
Maximum number of security groups per interface 5
Maximum number of VMs in a single placement group 5

2 Including the boot disk.

3 When starting a VM, a maximum of 14 devices, including the boot disk and a NIC, can be connected to it. Other devices must be connected to a running VM. Please note that, if you restart a VM with more than 14 devices connected, it won't be able to load and run.

VM limits on operations with non-replicated disks

Type of limit Value
Total number of non-replicated SSDs per placement group 8
Maximum4 IOPS per vCPU 10,000
Maximum4 IOPS per VM 100,000
Maximum5 bandwidth per vCPU 100 MB/s
Maximum5 bandwidth per VM 1 GB/s

Disk and file storage limits

Network SSD
Network HDD
Non-replicated SSD
Type of limit Value
Maximum disk size 256 TB
Allocation unit size 32 GB
Maximum4 IOPS for writes per disk 40000
Maximum4 IOPS for writes per allocation unit 1000
Maximum5 bandwidth for writes per disk 450 MB/s
Maximum5 bandwidth for writes per allocation unit 15 MB/s
Maximum4 IOPS for reads per disk 20 000
Maximum4 IOPS for reads per allocation unit 1000
Maximum5 bandwidth for reads per disk 450 MB/s
Maximum5 bandwidth for reads per allocation unit 15 MB/s
Type of limit Value
Maximum disk size 256 TB
Allocation unit size 256 GB
Maximum4 IOPS for writes per disk 11000
Maximum4 IOPS for writes per allocation unit 300
Maximum5 bandwidth for writes per disk 240 MB/s
Maximum5 bandwidth for writes per allocation unit 30 MB/s
Maximum4 IOPS for reads per disk 2000
Maximum4 IOPS for reads per allocation unit 300
Maximum5 bandwidth for reads per disk 240 MB/s
Maximum5 bandwidth for reads per allocation unit 30 MB/s
Type of limit Value
Minimum non-replicated disk size 93 GB
Allocation unit size 93 GB
Maximum4 IOPS for writes per disk 75 000
(achievable for
connections via vhost,
otherwise a maximum of 50000)
Maximum4 IOPS for writes per allocation unit 5600
Maximum5 bandwidth for writes per disk 1 GB/s
Maximum5 bandwidth for writes per allocation unit 82 MB/s
Maximum4 IOPS for reads per disk 75 000
(achievable for
connections via vhost,
otherwise a maximum of 50000)
Maximum4 IOPS for reads per allocation unit 28,000
Maximum5 bandwidth for reads per disk 1 GB/s
Maximum5 bandwidth for reads per allocation unit 110 MB/s
SSD storage
HDD storage
Type of limit Value
Maximum storage size 8 TB
Allocation unit size 32 GB
Maximum number of files in storage 1000000
Maximum size of one file in storage 300 GB
Type of limit Value
Maximum storage size 8 TB
Allocation unit size 256 GB
Maximum number of files in storage 1000000
Maximum size of one file in storage 300 GB

Read and write operations utilize the same disk resource. The more read operations you do, the fewer write operations you can do, and vice versa. For more information, see Read and write operations.

4 To achieve maximum IOPS, we recommend performing read and write operations whose size is close to that of the disk block (4 KB by default).

5 To achieve the maximum possible bandwidth, we recommend performing 4 MB reads and writes.

Limits of disk snapshot schedules

Type of limit Value
Number of disks included in a schedule 1000
Number of schedules to add a disk to 1000

Yandex Object Storage

Quotas

Type of limit Value
Storage volume in a cloud 1 TB
Number of buckets per cloud 25

Limits

Type of limit Value
Maximum object size 5 TB
Total header size per request to the HTTP API 8 KB
Size of user-defined metadata in an object 2 KB
Maximum size of data to be uploaded per request 5 GB
Minimum size of data parts for multipart uploading, except the last one 5 MB
Maximum number of parts in multi-part uploading 10,000
Maximum bucket access policy size 20 KB

Yandex Virtual Private Cloud

Quotas

Type of limit Value
Number of cloud networks per cloud 2
Number of subnets per cloud 6
Number of all public IP addresses per cloud 8
Number of static public IP addresses per cloud 2
Number of routing tables per cloud 8
Number of static routes per cloud 256
Maximum number of security groups 10

Limits

Type of limit Value
Minimum CIDR size for a subnet /28
Maximum CIDR size for a subnet /16
Maximum number of TCP/UDP connections per VM* 50000
Supported network and transport layer protocols IP, ICMP, TCP, UDP, and GRE
Maximum number of security groups per interface 5
Maximum number of rules per security group 50
Maximum number of CIDRs per rule 50
Size of the DNS server IP address list 100 characters

* All TCP/IP and UDP connections opened and half-opened within 180 seconds are taken into account. If there are no data or keep-alive packets in the connection during this time, it is forcibly closed.

Outgoing traffic filtering

Yandex Cloud always blocks outgoing traffic from Virtual Private Cloud public IP addresses to TCP port 25 of any servers on the internet (except for Yandex Mail servers) and Yandex Compute Cloud VMs.

Yandex Cloud may open TCP port 25 by request via technical support if you comply with Acceptable Use Policy. Yandex Cloud is entitled to block outgoing traffic on TCP port 25 if you violate the Use Policy.

Yandex Resource Manager

There are no quotas or limits for Yandex Resource Manager.

Yandex Network Load Balancer

Quotas

Type of limit Value
Number of load balancers per cloud 2
Number of target groups per cloud 2

Limits

Type of limit Value
Number of resources per target group 254
Number of listening ports 10
Number of health checks per attached target group 1
Status check protocol TCP, HTTP

Other restrictions

A particular target group can only contain target resources from a single cloud network.

A target group can include resources that are connected to the same subnet within a single availability zone.

You can create a load balancer without a listener.

Health checks are transmitted from the IP address range 198.18.235.0/24.

When connecting resources to the load balancer, keep in mind the limit on the maximum number of simultaneous TCP/UDP connections per VM.

Yandex Managed Service for ClickHouse

Quotas

Limits Value
Number of clusters per cloud 16
Total number of processor cores for all the database hosts in a cloud 96
Total virtual memory for all DBs per cloud 640 GB
Total storage capacity for all clusters per cloud 4096 GB

Limits

Limits Minimum value Maximum value
Host class b1.nano (2 × 5% vCPU Intel Broadwell, 2 GM RAM) m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM)
Number of ClickHouse hosts in a non-sharded cluster when using HDD network or SSD network storage 1 7
Number of ClickHouse hosts in a non-sharded cluster when using non-replicated SSD storage 3 7
Number of ClickHouse hosts in a non-sharded cluster when using local SSD storage 2 7
Number of shards in a sharded cluster 1 50
Number of hosts in a shard when using HDD network or SSD network storage 1 7
Number of hosts in a shard when using non-replicated SSD storage 3 7
Number of hosts in a shard when using local SSD storage 2 7
Total number of hosts per cluster 1 353 (50 shards × 7 hosts + 3 ZooKeeper hosts)
Amount of data on the host when using HDD network or SSD network storage 10 GB 4096 GB
Amount of data on the host when using non-replicated SSD storage 93 GB 8184 GB
Amount of data on the host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) 100 GB 1500 GB
Amount of data on the host when using local SSD storage (for Intel Ice Lake) 368 GB 2944 GB

Yandex Managed Service for MongoDB

Quotas

Limits Value
Number of clusters per cloud 16
Total number of processor cores for all DB hosts per cloud 96
Total virtual memory for all DB hosts per cloud 640 GB
Total storage capacity for all clusters per cloud 4096 GB

Limits

Limits Minimum value Maximum value
Host class b1.nano (2 × 5% vCPU Intel Broadwell, 2 GB RAM) m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM)
Number of shards per cluster 1 10
Number of hosts in a shard when using HDD or SSD network storage 1 7
Number of hosts in a shard when storing data on non-replicated or local SSDs* 3 7
Number of hosts per cluster 1 or 3 hosts depending on the storage type, a cluster is created non-sharded 70 (10 shards × 7 hosts)
Amount of data on the host when using HDD or SSD network storage 10 GB 1 TB
Amount of data on the host when using non-replicated SSD storage 93 GB 1 TB
Amount of data on the host when using local SSD storage* 100 GB 1 TB

* Read more about how a platform selection impacts available storage types.

The maximum available number of simultaneous connections to a single Managed Service for MongoDB cluster host depends on the amount of RAM on the host:

Amount of RAM Maximum number of connections
2 GB 2048
4 GB 4096
8 GB 8192
16 GB or higher 16 384

Yandex Managed Service for MySQL

Quotas

Limits Value
Number of clusters per cloud 16
Total number of processor cores for all DB hosts per cloud 96
Total virtual memory for all DB hosts per cloud 640 GB
Total storage capacity for all clusters per cloud 4096 GB

Limits

Limits Minimum value Maximum value
Host class b1.nano (2 × 5% vCPU Intel Broadwell, 2 GM RAM) m3-c80-m640 (80 vCPU Intel Cascade Lake, 640 GB RAM)
Number of hosts in a cluster when using HDD network or SSD network storage 1 7
Number of hosts in a cluster when storing data on non-replicated or local SSDs 3 7
Amount of data on the host when using SSD network storage 10 GB 4096 GB
Amount of data on the host when using HDD network storage 10 GB 2048 GB
Amount of data on the host when using non-replicated SSD storage 93 GB 8184 GB
Amount of data on the host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) 100 GB 1500 GB
Amount of data on the host when using local SSD storage (for Intel Ice Lake) 368 GB 2944 GB

Yandex Managed Service for PostgreSQL

Quotas

Type of limit Value
Connection time-to-live 12 hours
Number of clusters per cloud 16
Total number of processor cores for all the database hosts in a cloud 96
Total virtual memory for all DBs per cloud 640 GB
Total storage capacity for all clusters per cloud 4096 GB

Limits

Type of limit Minimum value Maximum value
Host class b1.nano (2 × 5% vCPU Intel Broadwell, 2 GB RAM) m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM)
Number of hosts in a cluster when using HDD network or SSD network storage 1 7
Number of hosts in a cluster when storing data on non-replicated or local SSDs 3 7
Amount of data on the host when using SSD network storage 10 GB 4096 GB
Amount of data on the host when using HDD network storage 10 GB 2048 GB
Amount of data on the host when using non-replicated SSD storage 93 GB 8184 GB
Amount of data on the host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) 100 GB 1500 GB
Amount of data on the host when using local SSD storage (for Intel Ice Lake) 368 GB 2944 GB

Yandex Managed Service for Redis

Quotas

Type of limit Value
Number of clusters per cloud 16
Total number of processor cores for all the database hosts in a cloud 64
Total virtual memory for all DBs per cloud 512 GB
Total storage capacity for all clusters per cloud 4096 GB

Limits

Type of limit Minimum value Maximum value
Host class b1.nano (burstable with 2 GB RAM) hm3-c32-m512 (32 vCPU Intel Ice Lake, 512 GB RAM)
Number of hosts in an unsharded cluster 1 or 3 depending on the disk type 7
Number of shards in a sharded cluster 3 10
Number of hosts in a shard when using SSD network storage 1 7
Number of hosts in a shard when using local SSD storage* 2 7
Number of hosts in a shard when using non-replicated SSD storage* 3 7
Number of hosts in a sharded cluster 3, 6, or 9 hosts depending on the disk type 70 (10 shards × 7 hosts)
Amount of data on the host when using SSD network storage Twice the amount of RAM selected 4096 GB
Amount of data on the host when using non-replicated SSD storage* Twice the amount of RAM selected, but no less than 93 GB 8184 GB
Amount of data on the host when using local SSD storage* Twice the amount of RAM selected, but no less than 100 GB 1500 GB
Number of cluster connections 65000

* Read more about how a platform selection impacts available storage types.

Yandex Message Queue

Quotas

Messages
Type of limit Value
Number of SendMessage and SendMessageBatch calls per queue 300 calls per second for standard queues

30 calls per second for FIFO queues
Number of ReceiveMessage calls per queue 300 calls per second for standard queues

30 calls per second for FIFO queues
Number of DeleteMessage and DeleteMessageBatch calls per queue 300 calls per second for standard queues

30 calls per second for FIFO queues
Number of ChangeMessageVisibility and ChangeMessageVisibilityBatch calls per queue 300 calls per second for standard queues

30 calls per second for FIFO queues
Number of CreateQueue calls per cloud 2 calls per second
Number of DeleteQueue calls per cloud 5 calls per second
Number of other request calls per cloud 100 calls per second
Number of queues per cloud 10

Limits

Queues
Type of limit Value
Minimum message enqueue delay (DelaySeconds parameter) 0 seconds
Maximum message enqueue delay (DelaySeconds parameter) 900 seconds (15 minutes)
Number of messages being processed per standard queue 120,000
Number of messages being processed per FIFO queue 20,000
Queue name Maximum of 80 characters, including numbers, small and capital Latin letters, hyphens, and underscores. The name of a FIFO queue must end with the .fifo suffix.
Messages
Type of limit Value
Batch entry ID Maximum of 80 characters, including numbers, small and capital Latin letters, hyphens, and underscores.
Maximum number of message attributes 10
Maximum number of entries per batch 10
Message content XML, JSON, and unformatted text. The following Unicode characters are supported:
  • #x9
  • #xA
  • #xD
  • from #x20 to #xD7FF
  • from #xE000 to #xFFFD
  • from #x10000 to #x10FFFF
Maximum period for retaining messages in a queue 1209600 seconds (14 days)
Minimum period for retaining messages in a queue 60 seconds (1 minute)
Maximum message enqueue delay (DelaySeconds parameter) 900 seconds (15 minutes)
Minimum message enqueue delay (DelaySeconds parameter) 0 seconds
Maximum message size 262144 bytes (256 KB)
Minimum message size 1 byte
Maximum message visibility timeout 12 hours
Minimum message visibility timeout 0 seconds
Maximum client message wait time in an empty queue. (the WaitTimeSeconds parameter) 20 seconds

Yandex SpeechKit

Quotas

Type of limit Value
Streaming recognition mode API v2
Requests per second 40
Number of concurrently running streams 60
Synchronous recognition
Requests per second 20
Asynchronous recognition
Recognition requests per hour 500
Operation status check requests per hour 2500
Billable hours of audio per day 10,000
Speech synthesis
Requests per second 40

Limits

Type of limit Value
Streaming recognition mode
Maximum duration of transmitted audio for the entire session 5 minutes
Maximum size of transmitted audio data 10 MB
Maximum number of audio channels 1
Synchronous recognition
Maximum file size 1 MB
Maximum duration of audio 30 seconds
Maximum number of audio channels 1
Asynchronous recognition
Maximum file size 1 GB
Maximum duration of audio 4 hours
Period for storing recognition results on the server 3 days
Speech synthesis
Maximum REST request size 5000 characters
Maximum gRPC request size 250 characters and 24 seconds

Yandex Translate

Quotas

Type of limit Value
Calls of a single API method per second 20
Characters sent for translation per hour 1 million
Characters sent for language detection per hour 1 million

Limits

For limitations on the field values in the request body, see the API reference.

The limits for using glossaries are as follows:

  • The number of pairs passed per glossary must be no more than 50.

  • The total number of characters in this structure must be no more than 20,000 in Unicode. 10,000 characters per source text and 10,000 characters per target text.

Warning

This only refers to texts without CGI parameters.

Yandex Vision

Quotas

Type of limit Value
Number of requests per second 10
Text recognition attempts per second 5
Face detection attempts per second 5
Image classification attempts per second 5

Limits

Type of limit Value
Maximum file size 1 MB
Maximum image size 20 MP (length × width)
Maximum number of pages in a PDF file 8

Was the article helpful?

Language / Region
Yandex project
© 2023 Yandex.Cloud LLC
In this article:
  • Service Level Agreement (SLA)
  • Support
  • Yandex Cloud Marketplace
  • Service quotas and limits
  • Yandex Compute Cloud
  • Yandex Object Storage
  • Yandex Virtual Private Cloud
  • Yandex Resource Manager
  • Yandex Network Load Balancer
  • Yandex Managed Service for ClickHouse
  • Yandex Managed Service for MongoDB
  • Yandex Managed Service for MySQL
  • Yandex Managed Service for PostgreSQL
  • Yandex Managed Service for Redis
  • Yandex Message Queue
  • Yandex SpeechKit
  • Yandex Translate
  • Yandex Vision