instances support the pay-by-bandwidth and pay-by-data-transfer metering methods. This topic describes the bandwidth limits of CLB instances that use different metering methods.
Bandwidth limits of CLB instances that use different metering methods
- The bandwidth limit of a pay-by-data-transfer CLB instance is used as a reference. It indicates the upper limit of the peak bandwidth. This upper limit is not a guaranteed value.
- The inbound bandwidth limit of a pay-by-bandwidth CLB instance equals its outbound bandwidth limit. You are charged only for the outbound bandwidth that is consumed to transmit data from Alibaba Cloud to the Internet.
- When CLB instances compete for resources, the system guarantees that the peak bandwidth of a pay-by-bandwidth CLB instance can reach the upper limit. However, the peak bandwidth of a pay-by-data-transfer CLB instance may be capped.
- The bandwidth limit of a pay-by-data-transfer instance may vary based on the region. The bandwidth value on the Instance Details page in the console shall prevail. If your workloads require higher bandwidth, you can use pay-by-bandwidth CLB instances that are billed on a pay-as-you-go or subscription basis. You can also associate an elastic IP address (EIP) with an internal-facing instance, purchase an EIP bandwidth plan for the CLB instance, and use the pay-by-95th-percentile metering method.
View the bandwidth limit of a pay-by-data-transfer CLB instance
To view the bandwidth limit of a pay-by-data-transfer CLB instance, perform the following steps:
- Log on to the CLB console.
- On the Instances page, click the ID of the CLB instance that you want to manage.
- Click the Instance Details tab and view Bandwidth.