Taking the networks required in the deployment of a CVM with Internet access as an example, this document explains each step in detail, from creating a VPC and subnet, to purchasing a CVM, assigning a public IP address, and lastly using a security group to control the inbound and outbound traffic of the CVM.
You can create a custom VPC and subnet, or you can skip this step by choosing to have the system automatically create a default VPC and subnet when purchasing the CVM.
A VPC includes at least one subnet. When a VPC is created, the system will create an initial subnet, and cloud service resources can only be added in the subnet.
The features of the default VPC are the same as those of the custom VPC that you create.
The CIDR blocks (IP ranges) of VPC instances and subnets cannot be modified once they are created. Therefore, complete network planning in advance.
Using custom VPC and subnet
In 1. Select the region and model in Custom Configuration, you can select the VPC and subnet created in Step 1 in the Network option, and the CVM will be created in the custom VPC and subnet.
Using default VPC and subnet
In 1. Select the region and model in Custom Configuration, you can select the default VPC (Default-VPC) and subnet (Default-subnet) in the Network option, and the CVM will be created in the default VPC and subnet.
We recommend that you assign a free public IP address when purchasing a CVM. If no public IP address is assigned during the purchase, you can bind the CVM to an elastic public IP address in CVM Console.
When purchasing a CVM, you can select the default security group (Default) of the system. This security group permits all traffic by default. You can set security group rules based on your needs.
After finishing configuring the CVM and security group, you need to configure the route table associated with the subnet.
You can purchase a NAT gateway to provide Internet access to CVMs without public IP addresses. For more information, see NAT Gateways.