Skip to content

VPC FAQ

View as Markdown

A private network in one region. Resources on it, such as nodes, load balancers, and databases, reach each other on private IPs, and that traffic stays off the public internet. See VPC.

Delhi and Chennai. A VPC belongs to one project and one region, and only resources in that region can join it.

Up to three in each region. To have more, write to cloud-platform@e2enetworks.com. See Create a VPC.

Should I use an E2E provided range or a custom one?

Section titled “Should I use an E2E provided range or a custom one?”

Use E2E provided IPv4 CIDR unless you need subnets or a range of your own. It gives you 512 addresses and works with CDP Backup, Monitoring, Security Compliance, and Kubernetes, which a custom range does not. See VPC address ranges.

Which address ranges can a custom VPC use?

Section titled “Which address ranges can a custom VPC use?”

A private range inside 10.0.0.0/8 or 172.16.0.0/12, from /16 to /28 in size, starting at its first address. The 192.168.0.0/16 block is refused. See VPC address ranges.

Can I change a VPC’s range or name later?

Section titled “Can I change a VPC’s range or name later?”

No. Both are set when you create the VPC. To use a different range, create a new VPC and move your resources to it. See Create a VPC.

No. Only a VPC with a custom range larger than /28 takes subnets. See Create a subnet.

Why do the first and last blocks of my range fail as subnets?

Section titled “Why do the first and last blocks of my range fail as subnets?”

E2E keeps addresses at the start and the end of every VPC’s range for the network itself, so those blocks do not have all their addresses free. Use the blocks in between. See VPC address ranges.

My subnet block is valid, so why is it refused?

Section titled “My subnet block is valid, so why is it refused?”

Usually because it overlaps addresses already in use, by another subnet or a resource, or reaches the addresses E2E keeps at either end of the range. The message is “Error while creating subnet, not enough available IPs”. See Troubleshooting VPC.

Choose the VPC under VPC when you create the node, or attach it afterward from the node’s Network tab. See Attach a node to a VPC.

Yes, once you peer them. A peering connection joins two of your VPCs, in the same project or different ones, in the same region or across Delhi and Chennai. See Peer two VPCs.

Yes. It travels through an encrypted tunnel between the two VPCs’ gateways. See Peer two VPCs.

Why do my peered resources not reach each other?

Section titled “Why do my peered resources not reach each other?”

Most often because the routes are missing on one side, or were lost when a resource restarted; run the commands from Show Commands on both sides again. A paused connection, overlapping ranges, or a security group that blocks the traffic have the same effect. See Troubleshooting VPC.

Can I connect a VPC to AWS or another cloud?

Section titled “Can I connect a VPC to AWS or another cloud?”

Yes, over a site-to-site VPN through a Firewall, E2E’s FortiGate appliance, placed in the VPC. Peering in MyAccount joins your own E2E VPCs only.

Hourly, or on a committed plan paid for a set term from 30 days to 1,095 days. Prices are on the E2E pricing page. See Convert a VPC to committed billing.

Can I delete a VPC that still has nodes on it?

Section titled “Can I delete a VPC that still has nodes on it?”

No. Remove every resource, subnet, and peering connection from it first. See Delete a VPC.