You can use elastic network interfaces (ENIs) to deploy high-availability clusters and perform low-cost failover and fine-grained network management. This topic describes how to separately create an ENI in the Elastic Compute Service (ECS) console.
Prerequisites
- A virtual private cloud (VPC) is created in a specified region and a vSwitch is created in the VPC. For more information, see Create and manage a VPC and Work with vSwitches.
- A security group is created in the specified VPC. For more information, see Create a security group.
Background information
- Create an ENI when you create an instance.
When you create an instance, you can bind only one primary and one secondary ENIs to the instance. If the secondary ENI is not unbound from the instance, the secondary ENI is released together with the instance. For more information, see Bind an ENI when you create an instance.
- Separately create an ENI.
ENIs that are separately created are secondary ENIs and can be bound to instances.
After ENIs are created, deleted, bound to instances, or unbound from instances, ENI operation events are triggered. You can use CloudMonitor to set notifications of ENI operation events to obtain the ENI operation results such as whether ENIs are created. For more information, see ENI operation event notifications.
Procedure
Result
What to do next
After you separately create an ENI, you can bind it to an instance. For more information, see Bind an ENI.