Functions

The EIP service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths.

You can assign EIPs, bind them to or unbind them from cloud resources, release EIPs, modify EIP bandwidth, and upgrade static BGP EIPs to dynamic BGP EIPs.

Figure 1 Connecting to the Internet using an EIP

For details, see Assigning an EIP.

Both IPv4 and IPv6 EIPs are available. You can assign an IPv6 EIP or map an existing IPv4 EIP to an IPv6 EIP.

After the IPv6 EIP function is enabled, you will obtain both an IPv4 EIP and its corresponding IPv6 EIP. External IPv6 addresses can access cloud resources through this IPv6 EIP.

Figure 2 Application scenarios and resource planning of IPv6 networks

For details, see IPv6 EIP Overview.

An EIP pool helps you manage a large number of EIPs and assigns EIPs with dynamic BGP routing, ensuring network stability and optimal user experience.

You can purchase and modify EIP pools.

For details, see EIP Pool Overview.

All ECSs, BMSs, and load balancers can share the same bandwidth if they reside in the same region and have EIPs bound.

You can assign, modify, delete a shared bandwidth, add EIPs to a shared bandwidth, and remove EIPs from a shared bandwidth.

You can enable and disable QoS.

For details, see Shared Bandwidth Overview.

Shared data package provides a quota for data usage. Such packages are cost-effective and easy to use. Shared data packages take effect immediately after your purchase. If you have subscribed to pay-per-use EIPs billed by traffic in a region and buy a shared data package in the same region, the EIPs will use the shared data package. After the package quota is used up or the package expires, the EIPs will continue to be billed on a pay-per-use basis.

For details, see Shared Data Package.

A global EIP can be bound to a global connection bandwidth for private communication and to a global internet bandwidth for global internet access. You can specify a global region and a global EIP pool to assign a global EIP, and bind a global EIP to an instance in any region on the cloud. 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 3 Global EIP architecture

For details, see Global EIP Overview.

Before binding a global EIP to an ECS, you need to create a global internet gateway to connect the VPC of the ECS to the global EIP so that the ECS can access the Internet through the global EIP. Global internet gateways are free of charge.

When you bind a global EIP to an ECS, the system automatically lists the global internet gateway of the VPC that the ECS belongs to, if there is one.

For details, see Global Internet Gateway Overview.

A global connection bandwidth can be bound to a central network to allow the resources to communicate with each other over the backbone network.

There are different types of global connection bandwidths that are designed for different application scenarios, including multi-city, geographic-region, and cross-geographic-region bandwidths. Geographic-region and cross-geographic-region bandwidths are often bound to Cloud Connect central networks.

Geographic-region bandwidths are used for resources in a geographic region to communicate.

Cross-geographic-region bandwidths are used for resources across geographic regions to communicate.

For details, see Global Connection Bandwidth Overview.

A global internet bandwidth can be shared by one or more global EIPs at the same time, improving bandwidth utilization.

Global internet bandwidths work together with global EIPs for Internet access. You can add one or more global EIPs to the same global internet bandwidth. A global EIP and its global internet bandwidth must use the same access point.

Figure 4 Global EIP architecture

For details, see Global Internet Bandwidth Overview.