forked from docs/virtual-private-cloud
proposalbot
b54a481241
VPC UMN Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com> Co-authored-by: proposalbot <proposalbot@otc-service.com> Co-committed-by: proposalbot <proposalbot@otc-service.com>
27 lines
1.3 KiB
ReStructuredText
27 lines
1.3 KiB
ReStructuredText
:original_name: vpc010004.html
|
|
|
|
.. _vpc010004:
|
|
|
|
Shared Bandwidth Overview
|
|
=========================
|
|
|
|
A shared bandwidth can be shared by multiple EIPs and controls the data transfer rate on these EIPs in a centralized manner. All ECSs, BMSs, and load balancers that have EIPs bound in the same region can share a bandwidth.
|
|
|
|
.. note::
|
|
|
|
- A shared bandwidth cannot control how much data can be transferred using a single EIP. Data transfer rate on EIPs cannot be customized.
|
|
|
|
When you host a large number of applications on the cloud, if each EIP uses a bandwidth, a lot of bandwidths are required, increasing O&M workload. If all EIPs share the same bandwidth, VPCs and the region-level bandwidth can be managed in a unified manner, simplifying O&M statistics and network operations cost settlement.
|
|
|
|
- Easy to Manage
|
|
|
|
Region-level bandwidth sharing and multiplexing simplify O&M statistics, management, and operations cost settlement.
|
|
|
|
- Flexible Operations
|
|
|
|
You can add EIPs (except for **5_gray** EIPs of dedicated load balancers) to or remove them from a shared bandwidth regardless of the type of instances that they are bound to.
|
|
|
|
.. note::
|
|
|
|
- Do not add EIPs of the dedicated load balancer type (**5_gray**) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.
|