Private networking (VPC)
How your VMs are kept on a private network of their own, and where to find their private addresses.
Your VMs get private networking automatically. There is nothing to create or switch on: each VM you launch gets a private IP address on a private network.
Find a VM's private IP
- Open Kridha ComputeMachines and select the prefix.
- Open the VM by clicking its card or its Super Id.
- In the General tab, look under Private Ip.
Each private address shows its CIDR, Gateway and mask. The public address, if the VM has one, is shown the same way under Public Ip.
Use the private IP when your VMs talk to each other, for example a web server connecting to a database server. The traffic stays on your private network.
Control what reaches each VM
Traffic profiles decide what traffic reaches each VM. To allow a connection, add a rule to a traffic profile and attach it to the VM. For example, to let only your web servers reach a database on port 5432, use an Inbound rule on the database VM with IP set to your private network's range (from the CIDR in Private Ip) and Port Range 5432:5432.
See Traffic profiles.
What's coming
Self-service VPC settings are coming soon. The Kridha VPCStandard Core VPC and Kridha VPCEnterprise Grade VPC items in the sidebar don't open a screen yet, and the Attach IP tab in a VM's details is greyed out (Coming soon). Until then, your private network works as described above with no setup.
If you need a specific network layout now, contact support.