Introduction
An Elastic Network Interface (ENI) is bound to a CVM in a virtual private cloud (VPC) and can be freely migrated between multiple CVMs. ENIs are very helpful in configuring and managing networks and building highly reliable network solutions. You can bind multiple ENIs in the same availability zone to a CVM to implement a high-availability network solution. You can also bind multiple private IP addresses to an ENI to implement multi-IP deployment on a single host.
Product Features
Multiple Network Interfaces
In addition to the primary ENI that is automatically generated when a CVM is created, it supports binding with multiple secondary ENIs. ENIs can belong to different subnets in the same VPC and availability zone. Each network interface supports configuring an independent security group, and the subnet where the network interface is located can be configured with an independent routing and forwarding policy.
Flexible Migration
ENIs can be freely migrated between CVMs in the same VPC and availability zone. When an ENI is unbound from a CVM, the bound private IP, Elastic IP (EIP), and security group policy are retained. There is no need to reconfigure the association after migration.
Multiple IPs
Depending on the CVM configuration, the elastic network interface can support binding up to 30 private IP addresses, and each private IP can be bound to an independent EIP. A single CVM can open multiple identical ports through multiple elastic Ips. The binding relationship between the ENI and the private and public IP addresses does not change when the ENI is unbound from the CVM.
Independent Routing Forwarding
The CVM can be bound to ENIs located in different subnets in the same VPC and availability zone. Each subnet can independently set routing and forwarding policies to achieve network isolation. You can also set routing policies in the CVM to direct network traffic of a specific destination to different network interfaces.