If no virtual private cloud (VPC) is created in a region, you can specify the system to create a default VPC and a default vSwitch when you create an Elastic Compute Service (ECS) instance, a Classic Load Balancer (CLB) instance, or an ApsaraDB RDS instance. After the instance is created, a default VPC and a default vSwitch are created.
Features of default VPCs and default vSwitches
When you specify the system to create a default VPC, you can choose to create a default vSwitch in a random zone or a specified zone. The following table describes the features of default VPCs and default vSwitches.
Feature | Default VPC | Default vSwitch |
Quantity | Each region supports at most one default VPC. | A default vSwitch belongs to a default VPC. You can create only one default vSwitch in each zone. |
Subnet mask and available private IP addresses | The subnet mask of a default VPC is 16 bits in length. For example, the 172.31.0.0/16 CIDR block provides up to 65,532 private IP addresses. | The subnet mask of a default vSwitch is 20 bits in length. For example, the 172.16.0.0/20 CIDR block provides up to 4,092 private IP addresses. |
Quota | Default VPCs do not consume the VPC quota that is allocated to your Alibaba Cloud account. | Default vSwitches do not consume the vSwitch quota for a VPC. |
Creation method | Default VPCs are created by Alibaba Cloud. The VPCs that you create are custom VPCs. | Default vSwitches are created by Alibaba Cloud. The vSwitches that you create are custom vSwitches. |
Operations and specifications |
|
|
Cloud resources that support default VPCs and vSwitches
You can specify the system to create a default VPC and a default vSwitch when you create an ECS, CLB, or ApsaraDB RDS instance. For more information, see the following topics:
If you want the system to create a default VPC and a default vSwitch when you create an ECS instance, make sure that no VPC is created in the region.
