Network
VPC & VNet
Isolated private networks to compartmentalise your resources and decide for yourself what talks to what.
What VPC & VNet covers
Isolated or connected VNets
Each VPC is a logically isolated network with its own addressing plan. Inside it, create as many VNets as you need: an exposed VNet for your public services, a private VNet for your databases and internal systems, which must never be reachable from outside.
Subnets, firewall and sharing
Split your VNets into subnets and define your own routing tables. A firewall rule allows only the ports and addresses you choose towards a sensitive resource. A shared VNet grants read access to another organisation on your account, without duplicating infrastructure.
Native integration
Your networks stay compatible with load balancers, bastions, VPN gateways, Kubernetes clusters and managed databases. Attaching a resource requires no extra network configuration.