An edge elastic IP address (EIP) is a single-Internet service provider (ISP) public IP address that you can independently purchase and own. Edge EIPs can be associated with and disassociated from Edge Node Service (ENS) instances, Edge Load Balancer (ELB) instances, and edge NAT gateways at any time. An edge EIP is a NAT IP address that is mapped to the associated cloud resources by using NAT. Edge EIPs allow the associated cloud resources to access the Internet and provide Internet-facing services. Public IP addresses are decoupled from other cloud resources to meet diverse business requirements.
Features
Cloud resource decoupling: You can independently purchase and own an edge EIP without the need to purchase associated resources.
Elastic association: Edge EIPs can be associated with and disassociated from cloud resources at any time to prevent unnecessary billing.
Real-time network configuration: You can use edge EIPs after purchase and adjust the peak bandwidth at any time. The adjustment immediately takes effect.
Optimized metering method: You are charged for the larger one of inbound bandwidth and outbound bandwidth of all edge EIPs on a node based on the pay-by-95th-percentile metering method.
Differences between an edge EIP and the IP address of a public NIC on an ENS instance
Item | EIP | IP address of a public NIC on an ENS instance |
Supported network | Virtual private cloud (VPC) | VPC and classic network |
Used as an independent resource | Supported | Not supported |
Associated with and disassociated from an ENS instance at any time | Supported | Not supported |
Whether the IP address is visible on the network interface controller (NIC) of the ENS instance | Invisible | Visible |
Limits
You can associate an edge EIP with only one cloud resource. The edge EIP that you want to associate with a cloud resource must be in the Available state. After you associate an edge EIP with a cloud resource, the edge EIP immediately takes effect.
Limit | Description |
Limits on associating an edge EIP with an ENS instance |
Note If the ENS instance has a public NIC, we recommend that you do not associate an edge EIP with the ENS instance. Otherwise, network communication may be affected. |
Limits on associating an edge EIP with a NAT gateway | The NAT gateway and the edge EIP must be deployed on the same node. |
Limits on associating an edge EIP with an ELB instance |
|
Billing
You are charged for the larger one of inbound bandwidth and outbound bandwidth of all edge EIPs on a node based on the pay-by-95th-percentile metering method.
Starting from 00:00 on April 1, 2024, you will be charged for edge EIPs based on the following billing rules.
Item
Description
Billing method
Pay-as-you-go
Billing cycle
Monthly
Unit price
14.3 per month for each EIP
Billing rules
You are charged the sum of the fees for all EIPs configured in the current month.
Fee of an EIP = Unit price × Effective factor.
NoteEffective factor = Effective days/Total number of days in the current month. For example, the total number of days in June 2024 is 30. If a bill for June 2024 contains 26 valid days, the effective factor is 26/30=0.86666667.
Effective days: the number of days from the day when an EIP is created to the day when the EIP is released or to the end of the month if the EIP is not released in the month. Examples:
Example 1: If an EIP is created on June 5, 2024 and is released on June 25, 2024, the number of effective days in June 2024 is 21.
Example 2: If an EIP is created on June 5, 2024 and is used till the end of the month, the number of effective days in June 2024 is 26.