Parameter | Description |
Region | Displays the region where you want to create the VPC. |
Name | Enter a name for the VPC. |
IPv4 CIDR Block | Select a method to allocate an IPv4 CIDR block to the VPC. |
Enter an IPv4 CIDR Block | Enter a primary IPv4 CIDR block for the VPC. You can specify one of the following CIDR blocks or their subsets as the primary IPv4 CIDR block of the VPC: 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8. These CIDR blocks are standard private CIDR blocks as defined by Request for Comments (RFC) documents. The subnet mask must be 8 to 28 bits in length. Example: 192.168.0.0/24. You can also use a custom CIDR block other than 100.64.0.0/10, 224.0.0.0/4, 127.0.0.0/8, 169.254.0.0/16, and their subnets as the primary IPv4 CIDR block of the VPC. In scenarios where multiple VPCs are used or in hybrid cloud scenarios where data centers and VPCs are used, we recommend that you use subsets of standard RFC CIDR blocks as VPC CIDR blocks with subnet masks no more than 16 bits in length. Make sure that the CIDR blocks of the VPCs do not overlap in both scenarios. In addition, the CIDR blocks of the VPCs cannot overlap with those of the data centers in hybrid cloud scenarios.
Note This parameter is required only if you set IPv4 CIDR Block to Manually enter an IPv4 CIDR block. After a VPC is created, you can add secondary IPv4 CIDR blocks to the VPC. For more information, see Add a secondary CIDR block.
|
Select Pool | Select an IPAM pool. Note This parameter is required only if you set IPv4 CIDR Block to IPv4 CIDR block allocated by IPAM. Make sure that an effective region is specified for the selected IPAM pool and CIDR blocks are provisioned to the IPAM pool. For more information, see Create an IPAM pool and Provision CIDR blocks.
|
Network Mask | Select a network mask. This parameter is required only if you set IPv4 CIDR Block to IPv4 CIDR block allocated by IPAM and an IPAM pool is specified in the Select Pool field. If the selected pool has multiple CIDR blocks, the system selects a CIDR block that meets the allocation rules after you specify Network Mask. Important The network mask must meet the following requirements: The network mask must fall within the valid CIDR range of the VPC, which is /8 to /28. The network mask must meet the allocation rules. The network mask must fall within the CIDR range of the provisioned CIDR blocks.
The following example is used in this topic: The valid CIDR range of the VPC is /8 to /28. The minimum mask for the IPAM pool is /4 and the maximum mask is /27. The following CIDR blocks are provisioned to the IPAM pool: 10.0.0.0/12, 10.16.0.0/14, and 10.20.0.0/15.
In this example, the network mask length for the IPv4 CIDR block allocated from the IPAM pool is /12 to /27. |
IPv6 CIDR Block | Specify whether to assign an IPv6 CIDR block to the VPC. In this example, Assign BGP (Multi-ISP) is selected. If you set this parameter to Assign (Alibaba Cloud), the system automatically creates an IPv6 gateway of Free Edition for this VPC, and assigns an IPv6 CIDR block with the subnet mask /56, such as 2408:4005:3c5:6e00::/56. By default, IPv6 addresses are used for communication only within private networks. If you want to use an IPv6 address to access the Internet or provide services for IPv6 clients over the Internet, you must purchase Internet bandwidth for the IPv6 address. For more information, see Enable and manage IPv6 Internet bandwidth. Note Only the following regions support IPv6 CIDR blocks: China (Hangzhou), China (Shanghai), China (Nanjing - Local Region), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Hong Kong), China (Fuzhou - Local Region), Japan (Tokyo), South Korea (Seoul), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), Thailand (Bangkok), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), SAU (Riyadh - Partner Region). After you create a VPC, you cannot change its IPv6 CIDR block. However, you can add a secondary IPv6 CIDR block to the VPC. For more information, see Add a secondary CIDR block.
|
Description | Enter a description for the VPC. |
vSwitch |
Name | Enter a name for the vSwitch. |
Zone | In the drop-down list, select a zone for the vSwitch. In the same VPC, vSwitches in different zones can communicate with each other. The drop-down list shows whether Elastic Compute Service (ECS) instances, ApsaraDB RDS instances, internal-facing Classic Load Balancer (CLB) instances, and internal-facing Application Load Balancer (ALB) instances are supported in each zone. The supported cloud resources vary based on the zone and the creation time of the cloud resources. The instances provided in this topic are for reference only. The actual instances on the buy page shall prevail. |
IPv4 CIDR Block | Enter an IPv4 CIDR block for the vSwitch. When you specify a CIDR block for the vSwitch, take note of the following limits: The CIDR block of a vSwitch must be a subset of the CIDR block of the VPC to which the vSwitch belongs. For example, if the CIDR block of a VPC is 192.168.0.0/16, the CIDR block of a vSwitch in the VPC can range from 192.168.0.0/17 to 192.168.0.0/29. The first IP address and the last three IP addresses of a vSwitch CIDR block are reserved. For example, if a vSwitch CIDR block is 192.168.1.0/24, the IP addresses 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255 are reserved. If a vSwitch is required to communicate with vSwitches in other VPCs or with data centers, make sure that the CIDR block of the vSwitch does not overlap with the destination CIDR blocks.
Note After you create a vSwitch, you cannot change its CIDR block. |
IPv6 CIDR Block | Enable IPv6 and configure an IPv6 CIDR block for the vSwitch. Note If your VPC is assigned an IPv6 CIDR block, you must configure the IPv6 CIDR block of the vSwitch. If your VPC is not assigned an IPv6 CIDR block, you do not need to configure the IPv6 CIDR block of the vSwitch.
By default, the subnet mask of the IPv6 CIDR block for the vSwitch is /64. You can enter a decimal number from 0 to 255 to define the last 8 bits of the IPv6 CIDR block. For example, if the IPv6 CIDR block of the VPC is 2408:XXXX:XXXX:6e00::/56, you can enter 255 (ff in hexadecimal format) for the IPv6 CIDR block of the vSwitch. In this case, the IPv6 CIDR block of the vSwitch is 2408:XXXX:XXXX:6eff::/64. The first IPv6 address and last nine IPv6 addresses are reserved by the system. For example, if the IPv6 CIDR block of a vSwitch is 2408:XXXX:XXXX:6eff::/64, the first IPv6 address 2408:XXXX:XXXX:6eff:: and the last nine IPv6 addresses are reserved by the system: 2408:XXXX:XXXX:6eff:ffff:ffff:ffff:fff7, 2408:XXXX:XXXX:6eff:ffff:ffff:ffff:fff8, 2408:XXXX:XXXX:6eff:ffff:ffff:ffff:fff9, 2408:XXXX:XXXX:6eff:ffff:ffff:ffff:fffa, 2408:XXXX:XXXX:6eff:ffff:ffff:ffff:fffb, 2408:XXXX:XXXX:6eff:ffff:ffff:ffff:fffc, 2408:XXXX:XXXX:6eff:ffff:ffff:ffff:fffd, 2408:XXXX:XXXX:6eff:ffff:ffff:ffff:fffe, and 2408:XXXX:XXXX:6eff:ffff:ffff:ffff:ffff.
|
Click Resource Group and Tag to configure the resource group and tags. |
Resource Group | Select the resource group to which the VPC belongs. |
Tag Key | Select or enter a tag key. You can specify up to 20 tag keys. A tag key can be up to 128 characters in length and cannot contain http:// or https:// . It cannot start with acs: or aliyun . |
Tag Value | Select or enter a tag value. You can specify up to 20 tag values A tag value can be up to 128 characters in length and cannot contain http:// or https:// . It cannot start with acs: or aliyun . |