Before using VPC, you need to plan the number of VPCs and their IP ranges according to your business needs, avoiding issues caused by temporary scale-out.
During planning, you need to take the region, VPCs, the number of subnets, IP ranges, and route tables into account.
Plan VPC
Plan one VPC
If your operations are small and all deployed in the same region, while there is no need for network isolation, it is recommended to plan one VPC.
You can create multiple subnets and route tables in one VPC for fine-grained management of traffic.
Plan multiple VPCs
It is recommended to plan multiple VPCs in the following scenarios:
- Multiple services must be isolated from each other
Because private network interconnection is enabled by default in the same VPC, you need to plan multiple VPCs when different services in the same region need to be isolated.
Plan Subnet
Converge CloudEach VPC supports creating up to 10 subnets, with each subnet representing a block of IP addresses within the VPC. The subnet's IP range must be within or identical with the VPC's IP range.
The following points should be kept in mind when planning a subnet:
- Subnet Size and IP Capacity
When creating a subnet, make sure that the IP capacity of the IP range meets the demands. However, the subnet should not be too large in case no new subnets can be created during subsequent service expansion. - Subnet's IP Range
If the VPC to which the subnet belongs needs to communicate with other VPCs or IDCs, ensure that the subnet's IP range does not overlap with the peer's IP range. Otherwise, private network interconnection is impossible. - Service Needs
Within the same VPC, subnets can be divided according to business modules. For example, Web layer, logic layer and data layer are deployed in different subnets, and network ACL can be used for inter-subnet access control.
Plan IP Range
Converge CloudVPC CIDR supports any of the following private IP ranges:
10.0.0.0-10.255.255.255 (The mask range must be between 16 and 28.)
172.16.0.0-172.31.255.255 (The mask range must be between 16 and 28.)
192.168.0.0-192.168.255.255 (The mask range must be between 16 and 28.)
Non-standard IPv4 private IP ranges (The mask range must be between 16 and 28.)
Note:
Since September 16, 2020, VPCs began to support non-standard IPv4 private IP ranges (non-standard IPv4 private IP ranges are the three major private IP ranges not defined in RFC 1918). To use them, please
Application.
IP Range Description
About VPC Interconnection
- If you need to establish multiple VPCs, and there is a communication demand between the VPCs or between the VPC and the IDC, please avoid overlap of multiple VPC IP ranges and do not use peering connection.
- If the subnet IP ranges have overlapped, you can re-create your VPCs and purchase CVMs.
Plan Route Table
A route table is used to control the traffic direction within a subnet, and each subnet can only be bound to one route table. VPCs support default route tables and custom route tables.
Plan one Route Table
If the traffic direction requirements of different subnets in your VPCs are identical or similar, it is recommended to plan one route table. You can create different routing policies to control the traffic direction.
Plan multiple Route Tables
If the traffic direction requirements of different subnets in your VPCs are quite different, it is recommended to plan multiple route tables. Subnets with different requirements are each bound with corresponding routing tables. Traffic flow is controlled through routing policies.
