Virtual Private Cloud (VPC) is an isolation of virtual resources on a network level. This is similar to VRF on classic hardware routers. A VPC can also be called a “route domain” because all subnets within a VPC are IP-linked. Subnets in different VPCs are not IP-linked by default. Subnets, instances created with attached virtual network, DHCP options, route tables, VPN connections are created in a VPC or have a firm logical link to it.
Creating a VPC¶
Click to create a VPC.
In the new VPC creation dialog, enter a description and specify a CIDR block - a range of IP-addresses for the VPC in the form of a Classless Inter-Domain Routing (CIDR) block. Later, you will have to create new subnets from this range. Plan the CIDR so that the number of subnets that can be created within it, meets your requirements to project scaling and development.
On the one hand, the CIDR block must be capacious enough to contain necessary number of subnets; on the other hand, it shouldn’t overlap with other subnets, to which this VPC is planned to be attached.
Attention! Address must be specified in CIDR notation (<network address>/<network prefix>). Prefix can take values from 16 to 28.
Created VPC will be available for selection in the working area.
All attached to subnets instances have access to Internet under dynamically allocated by the Cloud public IP using source NAT (“one-to-many”) technology. Source NAT is applied only for outgoing from VPC network packets.
DHCP options association¶
Click “Associate DHCP options” to set previously created DHCP options.
Resetting DHCP options¶
Default DHCP options can be associated to the VPC by resetting DHCP options.
Click “More…” to open a list of additional actions that can be executed with the selected VPC.
Deleting a VPC¶
Click “Delete” to delete VPC. After confirmation, the VPC and all associated resources will be deleted.
In CROC Cloud Platform, by default, each VPC has a DNS-server which resolves names using CROC Cloud servers.
You can disable the VPC’s DNS-server by selecting the appropriate menu item in the “Private clouds” section of the management console.
The VPC’s DNS-server is available on the first IP-address of each subnet. For example, if your subnet is
172.31.0.0/24, then DNS-server will handle requests on
Click to change the VPC description.