EIP is a public IP address resource that can be purchased and owned independently. After EIP is bound to cloud resources, cloud resources can communicate with the public network through EIP. This document uses EIP binding to CVM as an example to introduce the EIP usage lifecycle.
Background
The lifecycle of an EIP includes applying for an EIP, binding an EIP to a CVM, unbinding an EIP to a CVM, and releasing an EIP.
- Apply for EIP: Apply for EIP resources based on actual usage needs.
- Bind EIP to CVM: Bind EIP to the CVM instance and communicate with the public network through EIP.
- Unbind EIP from CVM: After unbinding an EIP from a CVM instance, you can bind the EIP to other cloud resources. After you unbind an EIP from a CVM instance, the network of the corresponding CVM instance may be disconnected. Operate with caution.
- Release EIP: If you no longer need to use the EIP, you can release it. No fees are incurred after release, but be aware that you may not be able to retrieve it after release.
Prerequisites
Ensure that the EIP and the bound CVM instance are in the same region. You can view the region of the corresponding EIP and CVM instance in the EIP or Instance interface of the CVM console.
Directions
Step 1: Apply for EIP
- Log in to the CVM console and choose EIP in the left sidebar to enter the EIP interface.
- Select Region at the top of the EIP page and click Apply.
- In the pop-up Apply for EIP dialog box, perform the following operations:
| Parameter | Description |
|---|---|
| Selecting Region | Since EIP has a region attribute, select the region to which the EIP belongs. |
| Carrier | Specify the ISP attribute of the EIP. Currently, China Telecom, China Unicom, China Mobile, and the public network CAP are supported. |
| Billing Mode | Bill by traffic. |
| Max. Bandwidth | Set the bandwidth limit as needed and allocate bandwidth resources reasonably. |
| Quantity | Select the number of applications as needed and ensure that the total number of EIPs does not exceed the total product quota. For details, see Quota Limit. |
- Click Confirm to complete the EIP application.
- In the list, you can view the applied EIP, which is currently unbound.
Note:
We recommend that you bind unbound EIP to cloud resources in a timely to save IP resources.
Step 2: Bind EIP to CVM
- Log in to the CVM console, select EIP, and enter the EIP interface.
- In the Action column to the right of the target EIP, select More > Bind.
- In the Bind Resources window that pops up, click CVM, select the CVM instance to be bound, and then click Confirm.
Note:
If the CVM instance already has an ordinary public IP, you must release the ordinary public IP before you can bind the EIP.
The number of CVM instances that can be bound to an EIP varies depending on the CPU configuration of the CVM instance. See Limits.
4. In the Confirm Binding dialog box that pops up, click OK to complete the binding with the cloud resources.
Step 3: Unbind EIP from CVM
- Log in to the CVM console, select EIP, and enter the EIP interface.
- In the Action column to the right of the target EIP, click Unbind.
- In the Unbind EIP window that pops up, confirm the unbinding information and click Confirm.
Step 4: Release EIP
- Log in to the CVM console, select EIP, and enter the EIP interface.
- In the Action column to the right of the target EIP, select More > Release.
- In the window confirming the release of the selected EIP that pops up, check Confirm to Release the Above IP and click Release.
Related Information
- If you need to convert the ordinary public IP of the CVM to EIP, see Converting Ordinary Public IP to EIP.
- If you need to bind other cloud resources, such as NAT gateways and ENI, see Binding EIP to Cloud Resources.
- If you need to adjust the peak bandwidth of the EIP, see Adjusting Bandwidth.