<p><strong><span style="font-size:18px">Security and isolation</span></strong></p> <p>VPCs are logically completely isolated. There is no way to communicate by default. VPC are divided into DMZ, SF, and PTR network domains. The network domains are also isolated by default. You need to configure access policies to connect. These are designed to satisfy your needs of secure isolation.</p> <p><strong><span style="font-size:18px">Easy to use</span></strong></p> <p>Users can quickly create and manage VPCs through the Ping An Cloud Console, and can build your own cloud data centers after a few simple steps, while reducing the infrastructure investment and O&amp;M costs.</p> <p><strong><span style="font-size:18px">Access control</span></strong></p> <p>Users can flexibly control the inbound and outbound traffic of cloud host resources as well as the traffic between different network domains through establishing security group rules.</p> <p><strong><span style="font-size:18px">Flexible expansion</span></strong></p> <p>Ping An Cloud VPC provides different network domains and subnets. Users can create different network domains in VPC and divide different subnets like traditional networks to deploy various businesses. Users can also connect the VPC to the user&#39;s local data center and flexibly extend the network architecture.</p> <p><strong><span style="font-size:18px">Hybrid cloud deployment</span></strong></p> <p>By default, there is no interconnection between VPCs, and between VPC and the local data center of the tenant. Users can realize the interconnection between the public cloud and the local data center through the following Ping An Cloud products:</p> <p>&bull; <strong>Express connect</strong>&mdash;Connects different VPCs.</p> <p>&bull; <strong>VPN gateway</strong>&mdash;Connects<strong> </strong>the VPC and the local data center of a tenant.</p>