You have activated the CCN service, and all VPCs in your organization have been interconnected through CCN. By default, network instances added to CCN are interconnected.
In certain scenarios, you can divide different network zones in your organization network, and network instances in different zones are isolated from each other. This can be implemented through the custom route table feature of CCN. Specifically, you can plan different custom route tables for CCN and associate different network instances with them in order to isolate network instances.
The custom route table feature is currently in beta test. To try it out, please submit a ticket.
The network instances associated with CCN are divided into a test zone and a production zone. Network instances are interconnected within the same zone but isolated across zones.
As shown below, create two custom route tables for the CCN instance: the test route table and the production route table.
According to the isolation of network zones, two custom route tables need to be planned: the test route table and the production route table.
The routing plan of the custom route table is as follows:
|Item||Test Route Table||Production Route Table|
|Route reception policy||Receive the routes of the network instances in the network zone of the test environment, i.e., routes of the test frontend VPC and the test backend VPC.||Receive the routes of the network instances in the network zone of the production environment, i.e., routes of the production frontend VPC and the production backend VPC.|
|Bound network instance||Bind the network instances in the network zone of the test environment, i.e., the test frontend VPC and test backend VPC.||Bind the network instances in the network zone of the production environment, i.e., the production frontend VPC and production backend VPC.|