Use Limits Overview

Last updated: 2021-06-21 15:29:20

    Account Limits for Purchasing CVM Instances

    • You need to sign up for a Tencent Cloud account. For more information, see Signing up for a Tencent Cloud Account.
    • You need to go through identity verification before purchasing any CVM instances in the Chinese mainland. For more information, see Identity Verification Guide.
    • If you create a pay-as-you-go CVM, the system will freeze the cost of one-hour CVM usage. Make sure that your account has sufficient balance for the order.

    CVM Instance Use Limits

    • Virtualized software cannot be installed or re-virtualized (such as installing VMware or Hyper-V).
    • You cannot use sound cards or mount external hardware devices (such as USB flash drives, external disks, and U-keys).
    • The public gateway CVM is available only in Linux operating system.

    CVM Instance Purchase Limits

    • For each user, the quota of pay-as-you-go CVM instances in each availability zone is 30.
    • For more information, see Purchase Limits.

    Image Limits

    • Public images: no use limits.
    • Custom images: each region supports a maximum of 10 custom images.
    • Shared images: each custom image can be shared with a maximum of 50 Tencent Cloud users. Custom images can only be shared with accounts in the same region as the source account.
    • For more information, see Image Types.

    EIP Limits

    Quota limits

    Resources 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

    Limits on public IPs bound to a CVM

    Starting on 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:

    Note:

    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

    ENI Limits

    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
    Big Data Big Data D3 - - - - 6 - - - 8 8
    Big Data D2 - - - - 6 - - - 8 8

    Bandwidth Limits

    • Maximum outbound bandwidth (downstream bandwidth)

      • The following rules apply to instances created before 00:00, February 24, 2020:

        Network Billing MethodInstanceMaximum Bandwidth Range (Mbps)
        Instance Billing MethodInstance Configuration
        Bill-by-trafficPay-as-you-go instancesAll0-100
        Bill-by-bandwidthPay-as-you-go instancesAll0-100
        Bandwidth packageAll0-2000
      • The following rules apply to instances created after 00:00, February 24, 2020:

        Network Billing MethodInstanceMaximum Bandwidth Range (Mbps)
        Instance Billing MethodInstance Configuration
        Bill-by-trafficPay-as-you-go instancesAll0-100
        Bill-by-bandwidthPay-as-you-go instancesAll0-100
        Bandwidth packageAll0-2000
    • Maximum inbound bandwidth (upstream bandwidth)

      • If the fixed bandwidth you purchased is greater than 10 Mbps, Tencent Cloud will assign a public network inbound bandwidth equals to the purchased bandwidth.
      • If the fixed bandwidth you purchased is less than 10 Mbps, Tencent Cloud will assign 10-Mbps public network inbound bandwidth.

    Disk Limits

    LimitationsDescription
    Elastic cloud disk capabilityStarting 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 performanceI/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 mounted to a CVMA maximum of 20
    Number of snapshots in one region64 + Number of cloud disks in the region x 64
    Cloud disks mounted to a CVMThe CVM and cloud disks must be in the same availability zone.
    Snapshot rollbackSnapshot data can only be rolled back to the cloud disk where the snapshot was created.
    Type of cloud disks can be created using snapshotsOnly snapshots of data disks can be used to create new elastic cloud disks.
    Size of cloud disks created using snapshotsThe size of cloud disks created using snapshots must be larger than or equal to that of the source cloud disk.

    Security Group Limits

    • Security groups are region-specific. A CVM can only be bound to security groups in the same region.
    • Security groups are applicable to CVM instances in any network environment.
    • Each user can configure a maximum of 50 security groups for each project in a region.
    • A maximum of 100 inbound or outbound rules can be configured for a security group.
    • One CVM can be associated with multiple security groups, and a security group can be associated with multiple CVM instances.
    • Security groups associated with CVMs on the classic network cannot filter packets from or to TencentDB (MySQL, MariaDB, SQL Server, or PostgreSQL) and NoSQL (Redis or Memcached) databases. Instead, you can use iptables to filter traffic for such instances.
    • The quotas are as shown below:
      ItemLimit
      Number of security groups50 per region
      Number of rules in a security group100 for inbound rules and 100 for outbound rules
      Number of CVM instances associated with a security group2,000
      Number of security groups associated with a CVM instance5
      Number of security groups that can be referenced by a security group10

    VPC Limits

    Resource Limit
    Number of VPCs per region for each 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