Application Scenarios
EIP Application Scenarios
EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways, or load balancers.
Binding an EIP to an ECS
Scenario
You can bind an EIP to an ECS to enable the ECS to access the Internet.
Related Services
Binding an EIP to a NAT Gateway
Scenario
After an EIP is bound to a NAT gateway and SNAT and DNAT rules are added, multiple cloud servers (such as ECSs and BMSs) can use the same EIP to access the Internet and provide services accessible from the Internet.
An SNAT rule allows servers in a specific VPC subnet to use the same EIP to access the Internet.
A DNAT rule enables servers in a VPC to provide services accessible from the Internet.
Related Services
NAT Gateway, ECS, BMS and VPC
Binding an EIP to a Load Balancer
A high-availability load balancing network can be built with the help of EIP.
To handle a large number of concurrent requests from the Internet, you can deploy multiple ECSs in a VPC and use ELB to distribute requests across these servers to improve service stability and availability.
Scenario
After you bind an EIP to a load balancer, the load balancer can distribute requests from the Internet to backend servers.
Related Services
ELB, ECS, and VPC
Global EIP Application Scenarios
You can bind a global EIP to a cloud instance (such as an ECS or load balancer) in any region on the cloud to enable communications with the Internet. A global EIP can be bound to a global connection bandwidth for private communications and to a global internet bandwidth for Internet access. 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.
Adding Global EIPs to a Global Connection Bandwidth for Private Communications
Scenario
To allow instances to communicate over the backbone network on the cloud, the global EIP of the instance should have a global connection bandwidth bound.
An example of binding a global EIP to an ECS:
The ECS with a global EIP bound is in CN East-Shanghai1, and the access point of the global EIP is CN East-Hangzhou. The type of the global connection bandwidth-A should be Multi-city.
Related Services
Global internet gateway, ECS, and VPC
Adding Global EIPs to a Global Internet Bandwidth for Internet Communications
Scenario
To enable an instance to communicate with the Internet, the global EIP of the instance should have a global internet bandwidth bound.
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 must have the same access point, that is, CN East-Hangzhou in this example.
Related Services
Global connection bandwidth, global internet gateway, ECS, and VPC
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
