You can bind an EIP to cloud resources such as CVM instances and NAT gateways and use EIP to flexibly provide disaster recovery and public network communication services.
Overview
- EIP is bound to the CVM instance. EIP is the public IP of the CVM instance. When a CVM instance fails, it can be unbound and rebound to a healthy CVM instance to help quickly restore services.
- EIP is bound to the NAT gateway, and port forwarding is configured using EIP so that resources on the CVM can be accessed from the public network.
- The EIP is bound to the private IP of the ENI, and the ENI is bound to the CVM instance to provide public network communication services for the CVM instance.
- The EIP is bound to the BMS and serves as the public IP of the BMS. When a BMS fails, it can be unbound and rebound to a healthy BMS to help quickly restore services.
Directions
Log in to the CVM console, select EIP, and enter the EIP interface.
On the EIP management page, select the region of the EIP to which you want to bind cloud resources, and click More > Bind in the operation column of the corresponding EIP.
Note:
If the EIP has been bound to cloud resources, unbind it first. For example, you need to replace the EIP of a faulty CVM instance with a healthy CVM instance.
In the Bind Resource window that pops up, select the cloud resource to which the EIP is to be bound and click Confirm.
| Bound Cloud Resources | Description |
|---|---|
| CVM Instance: | - The EIP is bound to the CVM instance. The CVM instance must not be bound to other EIPs and must not be allocated an ordinary public IP. - The EIP and CVM instances must be bound in the same region. - The number of CVM instances that can be bound to an EIP varies depending on the CPU configuration of the CVM instance. See Limits. |
| NAT Gateway | - The EIP and NAT gateway must be bound in the same region. - A NAT gateway can be bound to a maximum of 10 EIPs. - When a NAT gateway is bound to multiple EIPs, the system automatically performs a CLB. |
| Elastic Network Interface | - When an EIP is bound to the private IP of a primary network interface, the CVM instance bound to the primary network interface must not have an ordinary public IP allocated to it. - An EIP can only be bound to one private IP of the ENI. - When EIP is bound to the private IP of the secondary network interface, the secondary network interface has a public IP in addition to its private IP. You can bind multiple secondary network interfaces bound to EIP to the CVM instance and flexibly use multiple public IPs to provide public network communication services to the outside world, thus realizing a high-availability network solution. |
| BMS | EIP is bound to the BMS, providing the BMS with the ability to communicate with the public network. |
- In the pop-up confirmation dialog box, click OK to complete the binding with the cloud resources.
Next Steps
- If you need to unbind cloud resources from an EIP, see Unbinding Cloud Resources from EIP.
- If you need to adjust the peak bandwidth of the EIP, see Adjusting Bandwidth.