This topic describes the limits that apply to Elastic IP addresses and Elastic IP address associations with cloud resources.

General limits

The general limits of Elastic IP addresses are as follows:
  • You can create up to 20 Elastic IP addresses under one account. If you want to create more than 20 Elastic IP addresses, apply for a quota increase. For more information, see Manage quotas.
  • You can only associate one Elastic IP address with one cloud resource. Furthermore, the Elastic IP address must be in the available state. Associations take immediate effect upon complete configuration.
  • An Elastic IP address that is locked due to security reasons cannot be released, associated with or disassociated from any cloud resource.
  • The following table lists the limits on the peak bandwidth of Elastic IP addresses.
    Pay-by-data-transfer Elastic IP addresses Pay-by-bandwidth Elastic IP addresses
    Each Elastic IP address supports a peak bandwidth of 200 Mbit/s. The peak bandwidth of a pay-by-data-transfer Elastic IP address is for reference only and signifies the upper limit of bandwidth value. It is not a committed performance metric of the service. In the event of resource contention, the peak bandwidth may be limited. Each Elastic IP address supports a peak bandwidth of 500 Mbit/s. The peak bandwidth of a pay-by-bandwidth Elastic IP address is a committed performance metric of the service. In the event of resource contention, the peak bandwidth is guaranteed.
    The cumulative sum of the peak bandwidth values of all pay-by-data-transfer Elastic IP addresses in a single region cannot exceed 5 Gbit/s. If your service requires a guaranteed or larger peak bandwidth, you must use pay-by-bandwidth Elastic IP addresses instead. The cumulative sum of the peak bandwidth values of all pay-by-bandwidth Elastic IP addresses in a single region cannot exceed 50 Gbit/s. To increase the peak bandwidth, contact your account manager.
  • Elastic IP addresses purchased after 00:00 of February 15, 2020 also has the following inbound and outbound bandwidth limits:
    • Inbound bandwidth (the traffic that accesses the Elastic IP address)
      • If the peak bandwidth of the Elastic IP address is equal to or larger than 10 Mbit/s, Alibaba Cloud allocates an inbound peak bandwidth that is equal to the purchased peak bandwidth to the Elastic IP address.
      • If the peak bandwidth of the Elastic IP address is less than 10 Mbit/s, Alibaba Cloud allocates an inbound peak bandwidth of 10 Mbit/s to the Elastic IP address.
    • Outbound bandwidth (traffic from the Elastic IP address)

      Alibaba Cloud allocates an outbound peak bandwidth that is equal to the purchased peak bandwidth to the Elastic IP address.

Limits on associating ECS instances

Note the following limits before you associate an Elastic IP address with an Elastic Compute Service (ECS) instance:
  • The network type of the ECS instance must be Virtual Private Cloud (VPC).
  • The ECS instance and the Elastic IP address must belong to the same region.
  • The ECS instance must be in the running or stopped state.
  • The ECS instance is not associated with a public IP address or another Elastic IP address.
  • You can only associate one ECS instance with an Elastic IP address. If you want to associate multiple Elastic IP addresses with an ECS instance, you can associate the Elastic IP addresses with one or more secondary Elastic Network Interfaces (ENIs) and then associate the ENIs with the ECS instance. For more information, see Associate an ECS instance with multiple Elastic IP addresses.

Limits on associating NAT Gateways

Note the following limits before you associate an Elastic IP address with a NAT Gateway:
  • No bandwidth package was purchased under the account to which the NAT Gateway belongs before January 26, 2018.
  • The NAT Gateway and the Elastic IP address must belong to the same region.
  • You can only associate up to 20 Elastic IP addresses with a NAT Gateway. If you need more Elastic IP addresses, apply for a quota increase. For more information, see Manage quotas.

Limits on associating SLB instances

Note the following limits before you associate an Elastic IP address with a Server Load Balancer (SLB) instance:
  • The network type of the SLB instance must be VPC.
  • The SLB instance and the Elastic IP address must belong to the same region.
  • An SLB instance can be associated with only one Elastic IP address.

Limits on associating HaVips

Note the following limits before you associate an Elastic IP address with a High-Availability Virtual IP Address (HaVip):
  • The HaVip and the Elastic IP address must belong to the same region.
  • The HaVip must be in the Available or Allocated state.
  • An HaVip can be associated with only one Elastic IP address.

Limits on associating secondary ENIs

Note the following limits before you associate an Elastic IP address with a secondary ENI:
  • The network type of the secondary ENI must be VPC.
  • The secondary ENI and the Elastic IP address must belong to the same region.
  • You can associate an Elastic IP address with a secondary ENI in one of the three modes: NAT mode, cut-through mode, and multi-EIP to ENI mode.
    • In the NAT mode, the number of Elastic IP addresses with which a secondary ENI can be associated depends on the number of private IP addresses of the secondary ENI.
    • In the cut-through mode, a secondary ENI can only be associated with one Elastic IP address.
    • In the multi-EIP to ENI mode, a secondary ENI can be associated with up to ten Elastic IP addresses. To increase the quota, open a ticket.