Binding a Global EIP to an Instance

Scenarios

This section describes how to bind a global EIP to an instance, such as an ECS or a load balancer, to enable the instance to communicate with the Internet through the global EIP.

By default, a global EIP can be bound to instances in the same geographic region. To bind a global EIP to an instance in another geographic region, submit a service ticket.

Notes and Constraints

• A global EIP can be bound to only one instance at a time.
• After a global EIP is bound to an ECS, the VPC of the ECS cannot be changed, and no more EIP can be bound to the ECS.
• A global EIP cannot be bound to a shared load balancer.

Prerequisites

• The required instance (such as ECS or ELB) has been created.
• For an ECS, you also need to create a global internet gateway for the VPC that the ECS belongs to.

Procedure

1. Go to the global EIP list page.
2. In the global EIP list, search for or locate the target global EIP.
3. Locate the target global EIP, and click Bind Instance in the Progress column.

   The page for binding an instance is displayed.

4. Select the region that the instance to be bound is located.

   A global EIP can be bound to an instance in any region.

5. Select the type of the instance to be bound and then select the instance.
6. Select the global internet gateway to be bound.

   The system automatically lists the global internet gateway of the VPC that the instance belongs to, if there is one.

7. Click Next.
8. Configure Global Connection Bandwidth, Bandwidth Name, and Bandwidth as prompted.
9. Click OK.

   In the global EIP list, you can see that the global EIP has instance bound.

Related Operations

• (Mandatory) After a global EIP is bound to an instance, you need to bind a global connection bandwidth to the global EIP. For details, see Adding Instances to a Global Connection Bandwidth.
• You need to create a global internet gateway for the VPC of the ECS. For details, see Creating a Global Internet Gateway.