Trial period restrictions

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.

Technical support

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

Service quotas and limits

• Quotas are organizational restrictions that can be changed by technical support on request.
• Limits are technical restrictions due to the Yandex.Cloud architecture specifics. 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 SSD storage capacity per cloud	200 GB
Total HDD storage capacity per cloud	500 GB
Total number of disk snapshots per cloud	32
Total storage capacity of all disk snapshots per cloud	400 GB
Number of images per cloud	8
Number of instance groups per cloud	10
Total number of GPUs for all VMs per cloud*	0
Number of concurrent operations in the cloud	15
Maximum number of VM instances in a placement group	5
Maximum number of placement groups per cloud	2
Number of dedicated hosts per cloud*	0

* To create a VM with a GPU or a dedicated host, contact technical support.

VM limits

Type of limit	Value
Maximum number of vCPUs per VM	32 and 80 for Intel Broadwell and Intel Cascade Lake platforms, respectively
Maximum virtual memory per VM	256 GB and 640 GB for Intel Broadwell and Intel Cascade Lake platforms, respectively
Maximum number of disks connected to a single VM	7
Maximum number of GPUs connected to a single VM	4 and 8 GB for Intel Broadwell and Intel Cascade Lake platforms, respectively
Maximum number of vGPUs connected to a single VM	1
Maximum number of vCPUs for VMs with GPUs	32
Maximum RAM for VMs with GPUs	384
Maximum number of security groups per interface	5

VM with non-replicated disks limits

Type of limit	Value
Maximum* IOPS for 1 vCPU	10 000
Maximum* IOPS for 1 VM	100 000
Maximum** bandwidth for 1 vCPU	100 MB/s
Maximum** bandwidth for 1 VM	1 GB/s

Disk limits

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. Learn more in Disks.

*

To achieve maximum IOPS, we recommend performing read and write operations that are 4 KB and less.

**

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

Yandex Object Storage

Quotas

Type of limit	Value
Storage volume in a cloud	5 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

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 simultaneous TCP/UDP connections per VM	50,000
Supported network and transport layer protocols	IP, ICMP, TCP, UDP, 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

Outgoing traffic filtering

Yandex.Cloud always blocks outgoing traffic to TCP port 25:

• To any servers on the internet other than Yandex.Mail servers.
• To Yandex Compute Cloud VMs when accessed via a public IP address.

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

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

Limits

Type of limit	Value
Lowest host class	b1.nano (5% × 2 vCPU Intel Broadwell, 2 GB RAM)
Highest host class	m2.8xlarge (64 vCPU Intel Cascade Lake, 512 GB RAM)
Maximum number of shards per cluster	50
Maximum number of hosts per shard	7
Maximum number of hosts per cluster	353 (50 shards × 7 hosts + 3 ZooKeeper hosts)
Maximum amount of data on the host when using network storage	4096 GB
Maximum amount of data on the host when using local storage	1400 GB

Yandex Managed Service for MongoDB

Quotas

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

Limits

Type of limit	Value
Lowest host class	b1.nano (5% × 2 vCPU Intel Broadwell, 2 GB RAM)
Highest host class	m2.8xlarge (64 vCPU Intel Cascade Lake, 512 GB RAM)
Maximum number of shards per MongoDB cluster	10
Maximum number of hosts per shard	7
Maximum number of hosts per cluster	70 (10 shards × 7 hosts)
Maximum amount of data on the host when using network storage	605 GB
Maximum amount of data on the host when using local storage	500 GB
Maximum number of simultaneous connections to a single cluster host	Depends on the total amount of RAM on the host, see below

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

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

Limits

Type of limit	Value
Lowest host class	b1.nano (5% × 2 vCPU Intel Broadwell, 2 GB RAM)
Highest host class	m2.8xlarge (64 vCPU Intel Cascade Lake, 512 GB RAM)
Maximum number of hosts per cluster	7
Maximum amount of data when using network storage	2048 GB
Maximum amount of data when using local storage	1400 GB

Yandex Managed Service for PostgreSQL

Quotas

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

Limits

Type of limit	Value
Lowest host class	b1.nano (5% × 2 vCPU Intel Broadwell, 2 GB RAM)
Highest host class	m2.8xlarge (64 vCPU Intel Cascade Lake, 512 GB RAM)
Maximum number of hosts per cluster	7
Maximum amount of data when using network storage	2048 GB
Maximum amount of data when using local storage	1400 GB

Yandex Managed Service for Redis

Quotas

Type of limit	Value
Number of clusters per cloud	16
Total number of processor cores for all DB hosts per cloud	64
Total virtual memory for all hosts per cloud	512 GB
Total disk storage capacity for all clusters per cloud	4096 GB

Limits

Type of limit	Value
Lowest host class	b1.nano (burstable with 2 GB RAM)
Highest host class	hm1.9xlarge (high-memory with 256 GB RAM)
Maximum number of hosts per cluster	7
Minimum disk size per cluster	2 times more than the amount of RAM selected
Maximum disk size per cluster	8 times more than the amount of RAM selected

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 clients waiting time to wait for the message from an empty queue (WaitTimeSeconds parameter)	20 seconds

Yandex SpeechKit

Quotas

Type of limit	Value
Short audio recognition
Requests per second	20
Streaming mode of short audio recognition
Requests per second	40
Number of streams running simultaneously	60
Long audio 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
Short audio recognition
Maximum file size	1 MB
Maximum duration of audio	30 seconds
Maximum number of audio channels	1
Streaming mode of short audio recognition
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
Long audio 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 request size	5000 characters

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.

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