Create a VPC with an IPv4 CIDR block and bind an EIP to an ECS in the VPC to allow the ECS to access the Internet.

Create a VPC with an IPv6 CIDR block and create an ECS with an IPv6 address in the VPC, so that the ECS can access the Internet using the IPv6 address. 

A VPC provides an isolated virtual network for ECSs. You can configure and manage the network as required.

A VPC comes with a default subnet. If the default subnet cannot meet your requirements, you can create one.

You can create security groups and add ECSs in a VPC to different security groups to improve ECS access security. 

You can create a custom network ACL, but any newly created network ACL will be disabled by default. It will not have any inbound or outbound rules, or have any subnets associated.

You can create a custom route table if you do not want to use the default one.

A VPC flow log records information about the traffic going to and from a VPC.

Create a VPC peering connection between two VPCs in the same account and region.

Create a VPC peering connection between two VPCs in different accounts and the same region.

VPCs are isolated from each other. To connect two VPCs in the same region, you can use a VPC peering connection to route traffic between them using private IP addresses.

Before creating your VPCs, determine how many VPCs, the number of subnets, and what IP address ranges or connectivity options you will need.

Your on-premises data center communicates with Huawei Cloud through Direct Connect or VPN. A third-party virtual firewall is deployed on the cloud to filter traffic.

Before configuring policy-based routes for a multi-NIC ECS, you need to collect network information about the ECS.

VPC APIs include both native OpenStack APIs and extension APIs and allow you to use all functions provided by the VPC service. 

Create a VPC and subnet for an ECS by calling APIs.

Create a VPC.

Query all available versions of a native OpenStack API.