Configure Bandwidth Cap
After both source and destination point configurations, you need to configure the bandwidth cap of your private connect.
Last updated
After both source and destination point configurations, you need to configure the bandwidth cap of your private connect.
Last updated
Select your desired bandwidth cap between two access points of your Layer 2 private connect. The larger the bandwidth cap, the lower the unit price. You're recommended to set a bigger bandwidth cap.
Note
If you connect to a public cloud, the public cloud usually provides different access bandwidth specifications as follows. You will be charged for the nearest cap higher than your configuration as the cloud connect bandwidth. Your actual access bandwidth of the private connect is still what you have configured.
AWS: 50 Mbps, 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, and 10 Gbps.
Tencent Cloud: 50 Mbps, 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, 8 Gbps, 10 Gbps, 40 Gbps, and 100 Gbps.
Google Cloud: 50 Mbps, 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, 10 Gbps, 20 Gbps and 50 Gbps.
Alibaba Cloud: 50 Mbps, 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, 8 Gbps and 10 Gbps.
Azure Cloud: 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps and 10 Gbps.
After creating your private connect, see What to Do Next to active your points.
Check the states of your private connect to see whether it is active.
