A Virtual Private Cloud (VPC) is a logically isolated network space customized by users on a cloud platform. Within a VPC, you can freely define IP range, IP addresses, and routing policies. Therefore, Converge Cloud recommends that you choose a VPC.
To help you better use VPC, the following network planning suggestions are provided:
Determining the number of VPCs
Known features:
- VPC has regional attributes. By default, the private networks of cloud services in different regions are not interconnected. When cross-region communication is required, you can establish a peering connection to satisfy.
- By default, different VPC private networks in the same region cannot communicate with each other. When cross-VPC communication is required, you can establish a peering connection to satisfy.
- By default, different availability zones in the same VPC can communicate with each other through private networks.
Related Suggestions: - If your business requires the deployment of systems in multiple regions, you will inevitably need to use multiple VPCs. You can choose to establish a VPC in a region close to your customers to reduce access delay and increase access speed.
- If you have multiple business deployments in the current region and want to isolate the networks between different businesses, you can create a corresponding VPC for each business in the current region.
- If you do not need to deploy in multiple regions and do not need network isolation between businesses, you can use only one VPC.
Defining Subnet Division
Known Features:
- A subnet is a block of IP addresses within a VPC. All cloud resources in a VPC must be deployed in a subnet.
- In the same VPC, subnet IP range cannot be repeated.
- The initial private IP address is automatically allocated by Converge Cloud in the VPC IP range. Converge Cloud VPC CIDR supports the use of any of the three major private IP ranges. The IP address range is as follows. The mask range must be between 16 and -28. The specific value is determined by the VPC where the instance is located.
- 10.0.0.0-10.255.255.255
- 172.16.0.0-172.31.255.255
- 192.168.0.0-192.168.255.255
- After the VPC is created successfully, you can not modify the IP range.
Related Suggestions: - If it is just VPC subnet planning and does not involve network communication with the basic network or IDC, you can choose any of the above IP ranges to create a new subnet.
- If you need to communicate with the infrastructure network, please establish the network of 10.[0~47].0.0/16 and its subsets as required.
- If you need to establish a VPN, the VPC IP range and the peer IP range (your IDC IP range) cannot overlap, so be sure to avoid the peer IP range when creating a new subnet.
- When dividing the IP range, the IP capacity of the range should also be considered, that is, the number of available IP addresses.
- Finally, it is recommended that the services under the same VPC be divided into subnets according to business modules. For example, subnet A is used for the web layer, subnet B is used for the logic layer, and subnet C is used for the DB layer. This is conducive to combining network ACL for access control and filtering.
Defining Routing Policy
Known Features:
- A route table consists of multiple routing policies that control the outbound traffic direction of subnets in the VPC.
- Each subnet must be associated with one and only one route table.
- Each route table can be associated with multiple subnets.
- When a user creates a VPC, the system automatically generates a default route table for it. The default routing table means that the VPC and the private network can communicate with each other.
Related Suggestions: - If there is no need to perform special control on the traffic flow of the subnet, and the VPC private network is interconnected by default, the default routing table can be used without configuring a custom routing policy.