Skip to navigation

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

You want…ChooseInternet access for the VMs
A VM that is simply on the internetNo VPC when you deploy the VMIts own public IPv4, in and out
Private servers (databases, workers) that never touch the internet, and one or two public onesA VPC with Private onlyNone, unless you attach a Reserved IP to a VM
Private servers that can still download updates and call outside APIsA VPC with Managed NAT GatewayOutbound through one shared public IPv4. Inbound only through port forwarding.

A VPC isolates traffic between networks; a firewall group filters which ports are open. Most setups use both.

Terms on this page

TermMeaning
CIDRA way to write an address range: 10.10.0.0/24 means the 256 addresses 10.10.0.0–10.10.0.255. A smaller number after the slash means a bigger range.
Private address rangeAddresses reserved for private networks (RFC 1918): 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16. A VPC must use one of these.
SubnetA slice of the VPC’s range. Every VM in a VPC sits in one subnet.
NAT gatewayNAT means network address translation. The gateway lets private VMs share one public address for outgoing traffic.

How it works

  1. You create a VPC in one location with a private address range. IBEE creates it with a default subnet.
  2. You attach VMs in the same location to a subnet. Each VM gets a private address in that subnet.
  3. VMs in the VPC reach each other over those private addresses. VMs outside the VPC can’t reach them.
  4. 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

1

Open VPC

In the sidebar, under Network & Security, click VPC. The VPC Networks page opens. Click Create VPC.

2

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.

3

Choose connectivity

Under Connectivity:

OptionWhat it doesCost
Private only (default)“VMs receive private addresses only. Attach a Reserved IP later to expose one specific VM.”Included
Managed NAT Gateway”Private VMs share one public IPv4 for outbound internet without accepting unsolicited inbound traffic.”Billed while the NAT gateway exists. The summary shows the price for the location.
4

Choose the private IP range

Under Private IP Range:

  • Automatic (default): IBEE picks a free /22 range (1,024 addresses) from 10.144.0.0/12 that 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.
5

Create

Check the summary on the right and click Create VPC Network. You see “VPC provisioning started” (or “VPC and managed NAT gateway provisioning started”). The VPC is ready when its status is available.

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:

ip -4 addr show # shows this VM's VPC address, for example 10.144.0.5
ping -c 3 10.144.0.6 # the other VM's VPC address

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

1

Open Attach Node

Click Actions → Attach Node (or Attach Node on the Attached Nodes tab).

2

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.

3

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).

4

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.

5

Attach

Click Attach Node. The dialog follows the attachment until it completes.

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.

1

Open the rule form

Click Actions → Add Port Forwarding, or Add Rule in the NAT Port Forwarding section of the Overview tab. These controls appear only on Managed NAT Gateway VPCs.

2

Fill in the rule

FieldWhat to enter
Rule nameFor example SSH access
ProtocolTCP or UDP
External portPublic port on the NAT gateway, 1–65535. Each protocol and external port can be used by one rule only.
Destination typePrivate VM (one NAT-connected VM) or MetalLB VIP (a Virtual IP)
Internal IP or MetalLB VIPThe VM or Virtual IP to forward to
Internal portPort on the destination, 1–65535
NoteOptional reason for the access
Enable this ruleThe public port accepts traffic once the rule is active

The form previews the path, for example 203.0.113.10:2222 → 10.144.0.5:22.

3

Save

Click Add Rule. Each rule row has Edit, Enable/Disable and Delete; when editing, click Save Changes.

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.

curl "https://api.ibee.ai/v1/networking/sites?workspace_id=710995" \
-H "Authorization: Bearer $IBEE_TOKEN"

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).

curl -X POST "https://api.ibee.ai/v1/networking/vpcs?workspace_id=710995" \
-H "Authorization: Bearer $IBEE_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "production-vpc",
"site_id": "68b99bd78a8eda32ff3f16ea",
"connectivity_type": "nat_gateway",
"auto_cidr": true,
"create_default_subnet": true
}'
Portal optionAPI connectivity_type
Private onlyprivate
Managed NAT Gatewaynat_gateway
(not in the portal)public (the API default)
TaskOperation
Rename a VPC or change its descriptionPATCH /networking/vpcs/VPC-ID
Add or delete a subnetPOST /networking/vpcs/VPC-ID/subnets, DELETE .../subnets/SUBNET-ID
Attach or detach a VMPOST /networking/vpcs/VPC-ID/nodes (with vm_id, subnet_id, connectivity private, nat or public_ip, and optional requested_private_ip), DELETE .../nodes/VM-ID
Create or delete a NAT gatewayPOST /networking/vpcs/VPC-ID/nat-gateways (optional reserved_public_ip_id), DELETE .../nat-gateways/NAT-GATEWAY-ID (optional body {"public_ip_action": "reserve"} or "release")
Put a Reserved IP on an existing NAT gatewayPUT .../nat-gateways/NAT-GATEWAY-ID/public-ip with {"reserved_public_ip_id": "..."}
Add, change or delete a port forwarding rulePOST .../nat-gateways/NAT-GATEWAY-ID/port-forwarding-rules, PATCH or DELETE .../port-forwarding-rules/RULE-ID. For a Virtual IP destination, use "target_type": "vip" with target_vm_ids.
Delete a VPCDELETE /networking/vpcs/VPC-ID

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.

  1. Detach every VM on the Attached Nodes tab.
  2. Delete the NAT gateway, if there is one. To keep its address, choose Reserve this NAT IP.
  3. Delete every Virtual IP on the Reserved VIPs tab.
  4. 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.

Limits

ItemLimit
VPCs per workspace in one location5
VPCs per organization5 in one location, 10 in total
VPCs per account25
Subnets per VPC10
NAT gateways per VPC1
VPC range/22 (1,024 addresses) to /28 (16 addresses), private (RFC 1918) IPv4 only
Automatic rangeA /22 from 10.144.0.0/12
Subnet size/29 (8 addresses) or larger, inside the VPC range
OverlapVPCs in the same account can’t overlap; other accounts may use the same range
Name1–80 characters; description up to 500 characters
LocationOne per VPC; VMs must be in the same location
IP versionIPv4 only
CostThe VPC and its subnets are included. A NAT gateway is billed while it exists.

Troubleshooting

You seeWhat it meansWhat to do
”VPC quota exceeded for workspace/site; limit is 5. Delete an existing VPC or request a quota increase.” (409)You’ve reached a VPC limit (the message names which one)Delete a VPC you don’t need, or ask support for an increase.
”VPC CIDR overlaps another VPC in this account. …” (409)Your custom range overlaps one of your VPCsChoose another range, or use Automatic.
”VPC prefix must be between /22 and /28”The range is too big or too smallPick a Network size from /22 to /28.
”The automatic VPC CIDR pool is exhausted for this account” (409)No free /22 is left in 10.144.0.0/12 for your accountUse Custom CIDR with a range from 172.16.0.0/12 or 192.168.0.0/16.
”Subnet quota exceeded; limit is 10 per VPC”The VPC has 10 subnetsDelete a subnet, or use larger subnets.
”NAT gateway quota exceeded; limit is 1 per VPC”The VPC already has a NAT gatewayUse the existing one.
”Private IP 10.144.0.1 is reserved as the subnet gateway”You picked the gateway address for a VMChoose another address in the subnet.
”NAT Gateway billing SKU is unavailable for this location. Try again shortly.”The NAT gateway’s price-list item (SKU) for the location couldn’t be loadedWait a minute and try again, or choose Private only.
The VM you want isn’t in the Node listIt’s in another location, or already attachedCreate the VPC in the VM’s location, or detach the VM from its current VPC.
A private VM can’t reach the internetThe VPC is Private onlyUse a Managed NAT Gateway VPC, or attach a Reserved IP to the VM.
VMs in the VPC can’t reach each otherA firewall group blocks the port, or they’re in different VPCsCheck both VMs’ firewall groups and that both are on Attached Nodes of the same VPC.