Global EIP Overview

A global Elastic IP (global EIP) can be bound to a global connection bandwidth for private communication and to a global internet bandwidth for Internet access. You can specify a global region and a global EIP pool to assign a global EIP, and bind a global EIP to a cloud instance (such as ECS and load balancer) from any region. To enable an ECS to communicate with the Internet through a global EIP, you also need to bind a global internet gateway to the global EIP.

Figure 1 Global EIP architecture

**Table 1** Global EIP communication scenarios
Communication Scenario	Required Resource	Description	Example	Operation Instruction
Intra-cloud communication	Global EIPs Global connection bandwidths Instances bound to global EIPs, such as ECSs and load balancers	To enable an instance to communicate on the cloud, the global EIP of the instance should have a global connection bandwidth bound. Select a global connection bandwidth type based on the global EIP access point and the region where the instance is located. Each global connection bandwidth can only be bound to one global EIP at a time. For details, see Overview.	The access point of global EIP-A is CN East-Hangzhou. The load balancer with global EIP-A bound is located in CN East-Shanghai1. CN East-Hangzhou and CN East-Shanghai1 are close to each other and belong to CN East. The type of the global connection bandwidth-A should be multi-city. The access point of global EIP-B is CN East-Hangzhou. The ECS-B with global EIP-B bound is located in CN South-Guangzhou. CN East-Hangzhou and CN South-Guangzhou are not close to each other but belong to the same geographic region. The type of the global connection bandwidth-B should be geographic-region. The access point of global EIP-C is CN East-Hangzhou. The ECS-C with global EIP-C bound is located in CN-Hong Kong. CN East-Hangzhou and CN-Hong Kong belong to different geographic regions. The type of the global connection bandwidth-C should be cross-geographic-region.	Assigning a Global EIP Binding a Global EIP to an Instance: Each global EIP can only be bound to one instance at a time. Adding Instances to a Global Connection Bandwidth: Each global connection bandwidth can only be used by one global EIP at a time.
Internet communication	Global EIPs Global internet bandwidth Instances bound to global EIPs, such as ECSs and load balancers	To enable an instance to communicate with the Internet, the global EIP of the instance should have a global internet bandwidth bound. The global EIP and the global internet bandwidth must have the same access point. Multiple global EIPs can be added to the same global internet bandwidth. For details, see Overview.	Global EIP-A, global EIP-B, and global EIP-C are added to global internet bandwidth-A. The global EIPs and the global internet bandwidth use the same access point, that is, CN East-Hangzhou.	Buying a Global Internet Bandwidth Adding Global EIPs to a Global Internet Bandwidth

Global EIP Quotas

You can log in to the console to query your global EIP quotas.

If you want to increase your quota, see How Do I Apply for a Higher Quota?

Your request for a larger quota will only be approved if your account has valid orders and you are continuously using cloud resources. If you have released resources immediately after subscribing to them multiple times, your request for quota increase will be declined.
If you have increased the global EIP quota but you have not used the quota for a long time, Huawei Cloud will reduce the quota to the default value.

Notes and Constraints

Global EIPs cannot be used independently. You need to bind them to cloud instances, such as ECSs and load balancers. For details, see Binding a Global EIP to an Instance.
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.

Parent topic: Global EIPs

Previous topic: Global EIPs

Next topic: Assigning a Global EIP