Before using Tencent Cloud VPC, you need to plan the quantity and IP range of your VPC instances based on your business to prevent problems resulting from temporary scale-out or similar.
During planning, pay attention to the belonging region, VPC instances, number of subnets, IP ranges, and route tables.
Each VPC belongs to a specific region (for example, Guangzhou), and each region contains one or more availability zones (such as Guangzhou Zone 1 and Guangzhou Zone 2). You can choose an appropriate region to create VPC instances and subnets.
Note that even if two VPC instances are present in the same region and isolated from each other by default within the private network, private network communication is enabled only in the same VPC by default. To enable private network communication between different VPC instances, establish a peering connection or use CCN.
If your business volume is relatively small and the business is deployed in the same region without the demand for network isolation, we recommend that you plan one VPC.
You can create multiple subnets and route tables in a single VPC to achieve refined traffic management.
In the following scenarios, we recommend that you plan multiple VPC instances:
Each Tencent Cloud VPC supports creating a maximum of 10 subnets, which are IP address blocks within VPC instances. The IP range of subnets must fall within or be identical to the VPC’s IP range. One VPC can simultaneously contain multiple subnets, and different subnets in the same VPC intercommunicate with each other through the private network by default.
Consider the following when planning subnets:
Tencent Cloud VPC CIDR supports using any of the following private IP ranges:
10.[0-47].0.0/16or its subsets. Classiclink cannot be created for VPC instances in other IP ranges.
A route table is used to control the traffic route within a subnet. Each subnet can be bound to one route table. Tencent Cloud VPC instances support the default route table and custom route tables.
If the traffic route requirements of different subnets in your VPC are the same or similar, we recommend that you plan one route table. You can create different routing policies to control different traffic routes.
If the traffic route requirements of different subnets in your VPC are different, we recommend that you plan multiple route tables. To do this, bind subnets with corresponding route tables based on different requirements, and control specific traffic routes by defining routing policies.