VPC
A VPC (virtual private cloud) is a private network for your VMs in one location. VMs in the same VPC talk to each other over private addresses, such as 10.144.0.5, that can’t be reached from the internet. You decide whether the VPC’s VMs can reach the internet at all, and which of them the internet can reach.
Think of it as your own office network: everyone inside can talk to each other, and the door to the street is closed unless you open it.
When to use a VPC
A VPC isolates traffic between networks; a firewall group filters which ports are open. Most setups use both.
Terms on this page
How it works
- You create a VPC in one location with a private address range. IBEE creates it with a default subnet.
- You attach VMs in the same location to a subnet. Each VM gets a private address in that subnet.
- VMs in the VPC reach each other over those private addresses. VMs outside the VPC can’t reach them.
- Internet access depends on the connectivity you chose: none (Private only) or outbound through a NAT gateway (Managed NAT Gateway).
Before you begin
- A verified organization. See Verify your identity.
- The location of your VMs. A VPC belongs to one location, and only VMs in that location can attach to it.
- An address range that doesn’t overlap your other VPCs, if you want to choose it yourself. VPCs in the same account can’t overlap.
- For the API: an API token with Networking permission (
network.read,network.write) and your workspace ID.
Create a VPC
Open VPC
In the sidebar, under Network & Security, click VPC. The VPC Networks page opens. Click Create VPC.
Enter the details
Under VPC details, enter a Name (1–80 characters, for example production-vpc) and, optionally, a Description. Under Location, choose where the VPC lives.
Choose the private IP range
Under Private IP Range:
- Automatic (default): IBEE picks a free
/22range (1,024 addresses) from10.144.0.0/12that doesn’t overlap your other VPCs. - Custom CIDR: enter a Network address (for example
10.10.0.0) and pick a Network size from/22(1,024 addresses) to/28(16 addresses); the default is/24(256 addresses). The range must be private (RFC 1918) and start on a boundary of its size; if it doesn’t, the form suggests the nearest valid address.
Verify
Open the VPC from the VPC Networks list. The Overview tab shows its name, location, private CIDR, connectivity, creation time and VPC ID. The Subnets tab shows the default subnet.
After you attach two VMs, check that they reach each other from inside one of them:
ping -c 3 sends 3 pings, 1 second apart. If none is answered, the other VM’s firewall group may not accept ICMP; test a port you know is open instead, for example nc -vz -w 5 10.144.0.6 22, which gives up after 5 seconds.
Subnets
A new VPC has one default subnet, so you can attach VMs straight away.
- Add a subnet: click Actions → Add Subnet (or Add Subnet on the Subnets tab). Enter a Name and a CIDR inside the VPC’s range that doesn’t overlap another subnet, for example
10.144.1.0/24. Click Create Subnet. A subnet must be/29(8 addresses) or larger. - Delete a subnet: on the Subnets tab, click the delete icon on its row. It’s deleted at once, without a confirmation step. Detach the VMs that use it first.
- See which addresses are taken: the Subnets tab lists every reserved and allocated address with its subnet, type, owner and status. In each subnet, the first address (network), the last (broadcast) and the gateway can’t be given to VMs.
VMs in a subnet use the DNS servers 1.1.1.1 and 8.8.8.8, unless you set others with the API’s dns field when you create the subnet.
Attach a VM
Choose the node and subnet
Select a Node (only VMs in the VPC’s location that aren’t attached yet are listed) and a Subnet.
Choose the private IP
Under Private IP assignment, choose Automatic (the next free address) or Specific address (an unused address inside the subnet; the network, broadcast and gateway addresses are refused).
Choose traffic routing (Managed NAT Gateway VPCs)
If the VM already has a network connection, choose:
- Use VPC for internet: internet and private traffic go through the VPC and its NAT gateway. The VM’s current public IP stays connected until you remove it in the VM’s networking settings.
- Private traffic only: the VM keeps its current internet connection and uses the VPC only for private traffic.
A VM with no other network connection uses the VPC as its main network. On a Private only VPC, a VM that already has a network connection uses the VPC for private traffic only.
The Attached Nodes tab lists each VM with its status, VPC address, subnet and access type (Private, NAT or Public IP). Some VMs need their network configuration refreshed inside the guest OS after a change; see Networking for VMs.
Detach a VM: on Attached Nodes, click the detach icon on its row, then Detach VM in the Detach VPC Interface dialog. You can attach it again later.
A VPC interface that is a VM’s only network path can’t be detached. Give the VM another path first (for example, attach it to another VPC and use that VPC for internet), then detach this one.
NAT gateway
A Managed NAT Gateway VPC starts with one NAT gateway. The Overview tab shows the gateway’s status and its public IP, and whether that address was assigned by IBEE or is one of your Reserved IPs.
- Use a Reserved IP as the gateway’s address: click Use Reserved IP (or Replace Reserved IP) on the gateway card, pick an unattached Reserved IP in the same workspace and location, and click Attach Reserved IP. Port forwarding rules move to the new address. A previous Reserved IP goes back to your Reserved IPs; an address IBEE assigned is released.
- Delete the gateway: click Delete NAT Gateway. VMs routed through it lose outbound internet (private traffic still works), all its port forwarding rules are deleted, and billing for it stops. Choose what happens to its address: Reserve this NAT IP (keep it as a Reserved IP, which is billed as one), Keep in Reserved IPs (when it already was one), or Release this IP (you may not get it back). Tick the confirmation box if VMs or rules are affected, then click Delete Gateway & Reserve IP or Delete Gateway & Release IP.
- Create a gateway again: on the Overview tab, click Create NAT Gateway (or Add Managed NAT on Attached Nodes). Choose Automatic NAT IP or one of your unattached Reserved IPs, and click Create NAT Gateway. Attached VMs use it without changes; deleted port forwarding rules are not restored.
NAT port forwarding
Port forwarding opens one public port on the NAT gateway and sends its traffic to a private VM, for example public port 2222 to SSH on 10.144.0.5:22.
The destination VM’s firewall group must still accept the Internal port.
Use the API
First list the locations that accept VPCs and copy the exact site_id of one where available is true. A site_id is an ID, not a location name.
Then create the VPC. Send connectivity_type every time: if you leave it out, the API creates a public VPC, a mode the portal doesn’t offer (VMs keep their own public interface and also get a private one).
The portal’s Use VPC for internet / Private traffic only choice when attaching a VM has no API field.
Delete a VPC
Deleting a VPC can’t be undone. Before you start, note which VMs use it: they lose their private addresses in it.
- Detach every VM on the Attached Nodes tab.
- Delete the NAT gateway, if there is one. To keep its address, choose Reserve this NAT IP.
- Delete every Virtual IP on the Reserved VIPs tab.
- Click Actions → Delete VPC (or the delete icon in the list), type the VPC’s name in the Delete VPC Network dialog, and click Delete VPC. Subnets are removed with the VPC.
If the VPC still has a NAT gateway and no VMs, the list’s dialog offers Delete NAT Gateway first, which releases an address IBEE assigned (a Reserved IP stays reserved). The API answers 409 Conflict while VMs, a gateway or Virtual IPs remain.
