Scenario

Cloud servers need to use the Internet to access Internet resources, or publish services.

Before You Begin

· You have purchased the EIP and ECS.

· The ECS has a NIC that is not bound to the EIP.

· The EIP is in an Unbound state.

Precautions

Binding an elastic IP does not require shutting down the VM, and it takes effect in real time after the binding is successful.

Procedure

Log in to the console. 

Select a region in the upper left corner of the Control Center.

Select Computing > Elastic Cloud Server to enter the cloud server console.

In the list of cloud servers, click the name of the cloud server to which you want to bind an elastic IP to enter the cloud server details page.

On the Elastic IP tab, click Bind Elastic IP, select the NIC in the pop-up page, select the elastic IP to be bound, and click OK to complete the binding.

After successful binding, you can see the bound elastic IPs in the Elastic IP tab.

Description

If the billing method and expiration time of the elastic IPs and the cloud resource are inconsistent, one of them may expire and affect the overall business. For resource that is subscribed on a yearly or monthly basis, you need to pay special attention to the expiration time of resource and renew it before expiration. For pay-as-you-go resources you need to pay attention to the account balance and recharge in time before the balance is exhausted.

FAQs

Why can't EIP be bound to a cloud server instance?

Common reasons why EIP cannot be bound to the cloud server instance are as follows:

· EIP and cloud server instance are not in the same region.

· The cloud server instance has been assigned a fixed public IP or bound to other EIPs.

· If the cloud server instance is abnormal, only the running or stopped cloud server instance can be bound to the EIP.