Binding an EIP to an Instance

Scenarios

After EIPs are assigned, you can bind them to resources such as ECSs, BMSs, virtual IP addresses, NAT gateways, and load balancers to allow them to access the Internet.

Notes and Constraints

• If an EIP cannot be bound to an instance:
  There are instances, but an EIP cannot be bound to any of them.

  • An EIP can only be bound to an instance from its same region.
  • An EIP can only be bound to an instance from its same account.
  • The instance to be bound with an EIP is frozen.

  There are no instances.

  Buy an ECS, create a BMS, or assign a virtual IP address.

Procedure

Binding an EIP to an ECS, a BMS, or a virtual IP address

1. In the EIP list, locate the row that contains the target EIP, and click Bind.
2. Select the instance to which you want to bind the EIP.
   Figure 1 Bind EIP
   
3. Click OK.

Binding an EIP to a NAT gateway

After an EIP is bound to a NAT gateway, ECSs associated with this gateway can share the EIP to access the Internet or provide services accessible from the Internet.

You can bind an EIP to a NAT gateway by configuring SNAT and DNAT rules for the gateway. For details, see Configuring SNAT Rules to Enable Servers to Access the Internet and Configure DNAT Rules to Enable Servers to Provide Services Accessible from the Internet..

Binding an EIP to a load balancer

After an EIP is bound to a load balancer, the load balancer can receive requests over the Internet. For details, see Binding or Unbinding an EIP.