Elastic Network Interface (ENI) is an elastic interface for network access that binds Cloud Virtual Machine (CVM) servers on a Virtual Private Cloud (VPC) for seamless migration among multiple CVM servers. Multiple ENIs can be bound to one CVM server to create a highly available network.
An ENI is part of a subnet, which is part of a VPC, which in turn is part of an availability zone. An ENI can only be associated with a CVM instance in the same availability zone. Multiple ENIs can be associated with the same CVM instance. The specific number depends on the specification of the CVM.
- Primary ENI and secondary ENI: when you create a CVM instance, an ENI is automatically created in the process. That is the primary ENI. Any subsequent ENIs you create are secondary ENIs. You cannot bind or unbind a primary ENI. Secondary ENIs support binding and unbinding.
- :Primary private IP: the primary private IP of an ENI is assigned by the system or specified by the user when the ENI is created. You can modify the primary private IP of the primary ENI, but not those of secondary ENIs.
Secondary private IP: other than the primary private IP, all IP addresses bound to the ENI are secondary private IPs. You can bind/unbind these IPs.
- EIP: EIPs are mapped one-to-one to the private IPs of an ENI.
- Security group: an ENI can be associated with one or more security groups.
- MAC address: each ENI has a globally unique MAC address.
- Isolation among private network, public network, and management network:
Critical business often requires different routing policies and security groups for private networks, public networks, and management to ensure data security and network isolation. You can use CVM to achieve the same level of isolation as different physical servers. Simply assign different ENIs to different subnets.
- Highly reliable application deployment:*
Critical system components require multiple hot backups to ensure high availability. The flexible binding and unbinding of ENIs and private IPs is the foundation of Tencent Cloud’s high availability architecture. Use Keepalived to implement this feature.
The number of ENIs a CVM instance can be associated with and the number of private IPs an ENI can be associated with depend on the CPU and memory configurations. They are shown in the following table:
The number of IP addresses bound to a single ENI only represents the upper limit of IP addresses that ENIs can be bound to, not the available EIP quota. For the EIP quota of your account, please refer to EIP use limits.
||Number of ENIs
||Number of private IPs
|CPU: 1 core Memory: 1 GB
|CPU: 1 core Memory: > 1 GB
|CPU: 2 cores
|CPU: 4 cores Memory: < 16 GB
|CPU: 4 cores Memory: > 16 GB
|CPU: 8 - 12 cores
|CPU: > 12 cores
The following is a list of APIs related to ENI and CVM. For more information, refer to Overview of ENI APIs.