Based on CPU and memory configurations, the number of ENIs bound to a CVM differs from the number of private IPs bound to an ENI. The quotes are as shown below:
Note: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.
Model | Instance Type | Number of ENIs | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
CPU: 1 core | CPU: 2 cores | CPU: 4 cores | CPU: 6 cores | CPU: 8 cores | CPU: 10 cores | CPU: 12 cores | CPU: 14 cores | CPU: 16 cores | CPU: >16 cores | ||
Standard | Standard S5 | 2 | 4 | 4 | - | 6 | - | - | - | 8 | 8 |
Standard Storage Optimized S5se | - | - | 4 | - | 6 | - | - | - | 8 | 8 | |
Standard SA2 | 2 | 4 | 4 | - | 6 | - | - | - | 8 | 8 | |
Standard S4 | 2 | 4 | 4 | - | 6 | - | - | - | 8 | 8 | |
Standard Network-optimized SN3ne | 2 | 4 | 4 | - | 6 | - | 8 | - | 8 | 8 | |
Standard S3 | 2 | 4 | 4 | - | 6 | - | 8 | - | 8 | 8 | |
Standard SA1 | 2 | 2 | 4 | - | 6 | - | - | - | 8 | 8 | |
Standard S2 | 2 | 4 | 4 | - | 6 | - | 8 | - | 8 | 8 | |
Standard S1 | 2 | 4 | 4 | - | 6 | - | 8 | - | 8 | 8 | |
High IO | High IO IT5 | - | - | - | - | - | - | - | - | 8 | 8 |
High IO IT3 | - | - | - | - | - | - | - | - | 8 | 8 | |
MEM Optimized | Memory Optimized M5 | 2 | 4 | 4 | - | 6 | - | 8 | - | 8 | 8 |
Memory Optimized M4 | 2 | 4 | 4 | - | 6 | - | 8 | - | 8 | 8 | |
Memory Optimized M3 | 2 | 4 | 4 | - | 6 | - | 8 | - | 8 | 8 | |
Memory Optimized M2 | 2 | 4 | 4 | - | 6 | - | 8 | - | 8 | 8 | |
Memory Optimized M1 | 2 | 4 | 4 | - | 6 | - | 8 | - | 8 | 8 | |
Compute | Compute Optimized C4 | - | - | 4 | - | 6 | - | - | - | 8 | 8 |
Compute Network-optimized CN3 | - | - | 4 | - | 6 | - | - | - | 8 | 8 | |
Compute C3 | - | - | 4 | - | 6 | - | - | - | 8 | 8 | |
Compute C2 | - | - | 4 | - | 6 | - | - | - | 8 | 8 | |
GPU-based | GPU Compute GN6 | - | - | - | - | - | - | - | - | - | 8 |
GPU Compute GN6S | - | - | 4 | - | 6 | - | - | - | - | - | |
GPU Compute GN7 | - | - | 4 | - | 6 | - | - | - | - | 8 | |
GPU Compute GN8 | - | - | - | 4 | - | - | - | 8 | - | 8 | |
GPU Compute GN10X | - | - | - | - | 6 | - | - | - | - | 8 | |
GPU Compute GN10Xp | - | - | - | - | - | 6 | - | - | - | 8 | |
FPGA-based | FPGA Accelerated FX4 | - | - | - | - | - | 6 | - | - | - | 8 |
Big Data | Big Data D3 | - | - | - | - | 6 | - | - | - | 8 | 8 |
Big Data D2 | - | - | - | - | 6 | - | - | - | 8 | 8 | |
Big Data D1 | - | - | - | - | 6 | - | - | - | - | 8 | |
Cloud Physical Machine 2.0 | Not supported |
Maximum outbound bandwidth (downstream bandwidth)
The following rules apply to instances created after 00:00, February 24, 2020:
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 |
The following rules apply to instances created before 00:00, February 24, 2020:
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 |
Limitations | Description |
---|---|
Elastic cloud disk capability | Starting from May 2018, all data disks purchased with CVMs are elastic cloud disks, which can be detached and reattached to CVMs. This feature is supported in all availability zones. |
Cloud disk performance | I/O specification applies to both input and output performance at the same time. For example, if a 1-TB SSD has a maximum random IOPS of 26,000, it means that both its read and write performance 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 attached 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 attached 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. |
Repossession of cloud disks due to overdue payment | For specific repossession mechanism, please see Overdue Policy. |
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 security groups that can be referenced by a security group | 10 |
Resource | Limit |
---|---|
Number of VPCs per region per account | 20 |
Number of subnets per VPC | 100 |
Number of classic network-based 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 | 50 |
Number of default HAVIPs per VPC | 10 |
Was this page helpful?