Help Center/ Elastic IP/ User Guide (ME-Abu Dhabi Region)/ Getting Started/ Step 1: Create a VPC
Updated on 2025-11-05 GMT+08:00
View PDF
Share

Step 1: Create a VPC

Scenarios

Virtual Private Cloud (VPC) allows you to provision logically isolated virtual private networks for cloud resources, such as cloud servers, containers, and databases.

You can create a VPC, specify a CIDR block, and create one or more subnets for the VPC. A VPC comes with a default route table that enables subnets in the VPC to communicate with each other.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

    The Virtual Private Cloud page is displayed.

  3. Click Create VPC.

    The Create VPC page is displayed.

  4. On the Create VPC page, set parameters for the VPC and subnets as prompted.
    Table 1 VPC parameter description

    Parameter

    Description

    Example Value

    Region

    Regions are geographic areas isolated from each other. For low network latency and quick resource access, select the region nearest to where your services will be accessed.

    -

    Name
    The VPC name. The name:
    • Can contain 1 to 64 characters.
    • Can contain letters, digits, underscores (_), hyphens (-), and periods (.).

    vpc-test

    IPv4 CIDR Block

    The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC).

    The following CIDR blocks are supported:
    • 10.0.0.0/8–24
    • 172.16.0.0/12–24
    • 192.168.0.0/16–24

    10.0.0.0/8

    Enterprise Project

    The enterprise project to which the VPC belongs.

    An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.

    For details about creating and managing enterprise projects, see the Enterprise Management User Guide.

    default

    Advanced Settings > Tag

    The VPC tag. Click to expand the configuration area and set this parameter.

    Add tags to help you quickly identify, classify, and search for your VPCs.
    • Key: vpc_key1
    • Value: vpc-01
    Table 2 Subnet parameter descriptions

    Parameter

    Description

    Example Value

    AZ

    An AZ is a geographic location with independent power supply and network facilities in a region. AZs are physically isolated, and AZs in the same VPC are interconnected through an internal network.

    Each region contains multiple AZs. If one AZ is unavailable, other AZs in the same region continue to provide services.

    AZ1

    Name
    The subnet name. The name:
    • Can contain 1 to 64 characters.
    • Can contain letters, digits, underscores (_), hyphens (-), and periods (.).

    subnet-01

    IPv4 CIDR Block

    The IPv4 CIDR block of the subnet. A subnet is a unique CIDR block with a range of IP addresses in a VPC. Comply with the following principles when planning subnets:

    • Planning the CIDR block size: After a subnet is created, the CIDR block cannot be changed. You need to plan the CIDR block in advance based on the number of IP addresses required by your service.
      • The subnet CIDR block cannot be too small. Ensure that the number of available IP addresses in the subnet meets service requirements. Remember that the first and last three addresses in a subnet CIDR block are reserved for system use. For example, in subnet 10.0.0.0/24, 10.0.0.1 is the gateway address, 10.0.0.253 is the system interface address, 10.0.0.254 is used by DHCP, and 10.0.0.255 is the broadcast address.
      • The subnet CIDR block cannot be too large, either. If you use a CIDR block that is too large, you may not have enough CIDR blocks from the VPC available for new subnets, which can be a problem when you want to scale out services.
    • Avoiding subnet CIDR block conflicts: If you need to connect two VPCs or connect a VPC to an on-premises data center, the CIDR blocks to be connected cannot be the same.

    10.0.0.0/24

    IPv6 CIDR Block

    After the IPv6 function is enabled, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created.

    -

    Association Route Table

    The default route table with which the subnet will be associated. A route table contains a set of routes that are used to control the traffic routing for your subnets in a VPC. A default route table automatically comes with a VPC. Subnets in the VPC are automatically associated with the default route table. The default route table ensures that subnets in a VPC can communicate with each other.

    -

    Advanced Settings > Gateway

    The gateway address of the subnet. Click to expand the configuration area and set this parameter.

    Retain the default value unless there are special requirements.

    10.0.0.1

    Advanced Settings > DNS Server Address

    The gateway address of the subnet. Click to expand the configuration area and set this parameter.

    DNS server addresses allow ECSs in a VPC subnet to communicate with each other using private domain names. You can also directly access cloud services through private DNS servers.

    If you want to use other public DNS servers for resolution, you can change the default DNS server addresses. Changing the default DNS server addresses may cause communication failures in the subnet.

    100.125.x.x

    Advanced Settings > DHCP Lease Time

    The gateway address of the subnet. Click to expand the configuration area and set this parameter.

    The period during which a client can use an IP address automatically assigned by the DHCP server. After the lease time expires, a new IP address will be assigned to the client. Unit: Day or hour

    After you change the DHCP lease time on the console, the change is applied automatically when the DHCP lease of an instance (such as ECS) is renewed. You can wait for the system to renew the lease or manually renew the lease. Renewing lease will not change the IP address used by the instance. If you want the new lease time to take effect immediately, manually renew the lease or restart the ECS.

    -

    Advanced Settings > NTP Server Address

    The gateway address of the subnet. Click to expand the configuration area and set this parameter.

    If you want to add NTP server addresses for a subnet, you can specify NTP Server Address. The IP addresses are added in addition to the default NTP server addresses.

    • If you add or change the NTP server addresses of a subnet, you need to renew the DHCP lease for or restart all the ECSs in the subnet to make the change take effect immediately.
    • If the NTP server addresses have been cleared out, restarting the ECSs will not help. You must renew the DHCP lease for all ECSs to make the change take effect immediately.

    192.168.2.1

    Advanced Settings > Tag

    The gateway address of the subnet. Click to expand the configuration area and set this parameter.

    Add tags to help you quickly identify, classify, and search for your subnets.
    • Key: subnet_key1
    • Value: subnet-01

    Advanced Settings > Description

    The gateway address of the subnet. Click to expand the configuration area and set this parameter.

    Enter the description about the subnet in the text box as required.

    The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

    -
  5. Click Create Now.

    Return to the VPC list and view the new VPC.

Parent topic: Getting Started