Resource | Limit |
---|---|
Number of EIPs for each Tencent Cloud account in each region | 20 |
Number of daily purchase applications for each Tencent Cloud account in each region | Quota * 2 |
Number of times that public IP addresses can be reassigned to each account for free per day when an EIP is unbound | 10 |
Starting September 18, 2019, the maximum number of public IPs can be bound to a single CVM had changed based on CPU configuration. The quotas are as shown below:
This limit does not apply to CVM instances purchased before 00:00, September 18, 2019. For these instances, the number of public IPs can be bound to each instance is equal to the number of private IPs supported by your server.
Number of CPUs on a CVM | Maximum number of public IPs can be bound (including public and elastic IPs) |
---|---|
1–5 | 2 |
6–11 | 3 |
12–17 | 4 |
18–23 | 5 |
24–29 | 6 |
30–35 | 7 |
36–41 | 8 |
42–47 | 9 |
≥ 48 | 10 |
Based on CPU and memory configurations, the number of ENIs can be bound to a CVM differs from the number of private IPs can be bound to an ENI. The quotes are as shown below:
The number of IP addresses bound to a single ENI indicates the maximum number allowed. The EIP quota is not provided based on this upper limit but based on EIP use limits.
CVM configuration | Number of ENIs | Number of private IPs bound to a single ENI |
---|---|---|
CPU: 1 core Memory: 1 GB | 2 | 2 |
CPU: 1 core Memory: > 1 GB | 2 | 6 |
CPU: 2 cores | 2 | 10 |
CPU: 4 cores Memory: < 16 GB | 4 | 10 |
CPU: 4 cores Memory: > 16 GB | 4 | 20 |
CPU: 8–12 cores | 6 | 20 |
CPU: > 12 cores | 8 | 30 |
Maximum outbound bandwidth (downstream bandwidth)
For CVMs created before 00:00, February 24, 2020, the following rules apply:
Network Billing Method | Instance | Maximum Bandwidth Range (Mbps) | |
---|---|---|---|
Instance Billing Method | Instance Configuration | ||
Bill-by-traffic | Pay-as-you-go instances | All | 0–100 |
Bill-by-bandwidth | Pay-as-you-go instances | All | 0–100 |
Bandwidth package | All | 0–2000 |
For CVMs created after 00:00, February 24, 2020, the following rules apply:
Network Billing Method | Instance | Maximum Bandwidth Range (Mbps) | |
---|---|---|---|
Instance Billing Method | Instance Configuration | ||
Bill-by-traffic | Pay-as-you-go instances | All | 0–100 |
Bill-by-bandwidth | Pay-as-you-go instances | All | 0–100 |
Bandwidth package | All | 0–2000 |
Maximum inbound bandwidth (upstream bandwidth)
Limit Type | Description |
---|---|
Elastic cloud disk capability | Starting from May 2018, all data disks purchased with CVMs are elastic cloud disks, which can be unmounted from and remounted to CVMs. This feature is supported in all availability zones. |
Elastic cloud disk performance | I/O performance takes effect concurrently. For example, if a 1-TB SSD has a maximum random IOPS of 26,000, its IOPS for both reads and writes can reach this value. Due to performance limits, if the block size in this example is 4 KB or 8 KB, the maximum IOPS can be reached. If the block size is 16 KB, the maximum IOPS cannot be reached (throughput has already reached the limit of 260 MB/s.) |
Number of elastic cloud disks mounted to a CVM | A maximum of 20 |
Number of snapshots in one region | 64 + Number of cloud disks in the region x 64 |
Cloud disks mounted to a CVM | The CVM and cloud disks must be in the same availability zone. |
Snapshot rollback | Snapshot data can only be rolled back to the cloud disk where the snapshot was created. |
Type of cloud disks can be created using snapshots | Only snapshots of data disks can be used to create new elastic cloud disks. |
Size of cloud disks created using snapshots | The size of cloud disks created using snapshots must be larger than or equal to that of the source cloud disk. |
Item | Limit |
---|---|
Number of security groups | 50 per region |
Number of rules in a security group | 100 for inbound rules and 100 for outbound rules |
Number of CVM instances associated with a security group | 2,000 |
Number of security groups associated with a CVM instance | 5 |
Number of rules in each security group that reference the security group ID | 10 |
Resource | Limit |
---|---|
Number of VPC instances per region for each account | 5 |
Number of subnets per VPC | 10 |
Number of basic network CVMs can be associated with each VPC instance | 100 |
Number of route tables per VPC | 10 |
Number of route tables associated with each subnet | 1 |
Number of routing policies per route table | 100 |
Number of default HAVIPs per VPC | 10 |
Was this page helpful?