Last updated：2021-05-26 16:59:37
The Elastic IP (EIP) service provides public IP addresses. You can bind an EIP to a KEC, an EPC, or an SLB instance under your account. When an instance is faulty, you can detach the EIP from the instance and attach the EIP to another instance to ensure business continuity. EIP provides a variety of billing modes to address different business scenarios.
An EIP can only be bound to a KEC, an EPC, or an SLB instance in the same region. EIPs support dynamic binding and unbinding. You must note that:
One EIP can be bound to only one instance at a time.
One instance can be bound with only one EIP at a time.
If a KEC instance or an EPC instance in a VPC is bound with an EIP and is in a subnet associated with a NAT gateway, the packets sent to the Internet will first go through the EIP.
When the EIP of the instance is deleted, this IP address will be released to the public IP address pool of the VPC.
EIPs can be added to Bandwidth Share (BWS). For more information, see BWS documentation. The maximum bandwidth of each EIP that is added to the same BWS instance equals to the bandwidth range of the BWS instance. However, the total bandwidth of all the EIPs that are added to the same BWS instance at the same time point cannot exceed the upper bandwidth limit of the BWS instance. If the upper bandwidth limit of the BWS is reached, resource preemption will occur.
Did you find the above information helpful?
Please give us your feedback.
Thank you for your feedback.