Item | Bill-by-IP account | Bill-by-CVM account |
Whether the network bandwidth under the account can be migrated to other CVM instances | Yes, as the public network fees are billed by IP. | No, as the public network fees are billed on the bound CVM instance. |
Elastic IPv6 billing | IPv6 and IPv4 can be added into the same bandwidth package and billed together. | IPv6 can only be billed separately. |
NAT gateway billing | Bill by traffic and bill by bandwidth package are supported. | Only bill by traffic is supported. |
Is it necessary to purchase public network for CLB backend CVM | No. Only bandwidth needs to be purchased for CLB, which facilitates management. | Yes. Purchasing public network for all CLB backend CVMs is needed, which complicates management. |
New network-related features | Both the existing and new features are supported. | Only the existing features are supported. |
CVM Billing Mode | Network Billing Mode | Public IP | Impact |
Pay-as-you-go | Bill by hourly bandwidth | The instance has multiple public IPs | The network billing mode of all public IPs is converted to bill by traffic. No refund is involved. |
InternetChargeType
(billing mode) and InternetMaxBandwidthOut
(bandwidth cap) must be specified. For details, please see the API document AllocateAddresses.InternetChargeType
is set as BANDWIDTH_PACKAGE
(bill by bandwidth package), BandwidthPackageId
(ID of the bandwidth package to be added) must be specified.
Was this page helpful?