A private channel
Open a dedicated communication channel across your resources. No outside intrusion. No DDoS. No malicious connections.
Private Networks
Fast & secure data transfer inside your reliable infrastructure.
Fast & secure data transfer inside your reliable infrastructure.
Decrease intra-AZ latency
The fastest data link between your machines.
Monitor network usage
Control your connected resources using our console, API or command-line Interface.
Available zones:
Paris:PAR 1PAR 2PAR 3
Amsterdam:AMS 1AMS 2
Warsaw:WAW 1WAW 2
Tech specs
Private LANLayer 2 Ethernet network
High bandwidthUp to 4 Gbp/s between Instances
Multi-Private NetworksUp to 8 Private Networks per Instance
Scalability255 Instances per private network
A network interfaceConfigure any private IP addresses you want
QinQCarry your own VLANs over your private networks
Popular use cases
Build a distributed web application on General Purpose and Development Instances using a private network to communicate securely between them.
You can isolate some resources from the internet. For example you can host a MongoDB on a GP Instance, and make it accessible only from your frontend Instances.
Create a private network between your application's Managed Database and Instances, giving users the fastest access to data.
Take control of your network
Get started with tutorials
How to use Private NetworksLearn more
How to use Private Networks with your InstancesLearn more
How to use Object Storage with Private NetworksLearn more
Frequently asked questions
Private Networks is a managed cloud service allowing you to create layer 2 ethernet-switched domains. These domains can also be called a virtual LAN (VLAN). They are virtual, but completely private, local networks that securely connect your Instances together without necessarily exposing them publicly.
Private Networks is currently compatible with all our Instancess, our Elastic Metal offer, Managed Database, and Load Balancer. You’ll soon be able to connect Kubernetes Kapsule too.
Yes, you can configure multiple Private Networks on the same Instance. A virtual network interface is created for each private network to which the Instance is attached. You can bring up each of them as indicated in our product documentation.
You can configure:
- Up to 8 Private Networks per Instance
- Up to 255 Private Networks per Organization
- Up to 255 Instances per Private Network
No, instances are hot plugged to Private Networks. This means private network interfaces will appear on your Instances without needing to reboot.
Yes, you can configure IPv6 within Private Networks. To use it, the netmask should always be /64 and we recommend using a fc00::/7 unique local address (ULA) range. ULA IPv6 address generators are widely available for generating a personalized range.
No, they do not require a public IPv4 address.
Technically, any Ethernet payload should work over Private Networks. However, only IPv4 and IPv6 are officially supported. If you have real use cases for other protocols, let us know.