Private Networks are 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 Scaleway resources together without necessarily exposing them publicly. Scaleway resources including Instances, Elastic Metal servers, Load Balancers and Databases are all compatible with Private Networks.
Yes, you can configure multiple Private Networks on the same Scaleway resource. For example, in the case of Instances, you can connect multiple Private Networks to the same Instance. A virtual network interface is created for each Private Network the Instance is attached to. You can then bring up each of them as indicated in our documentation. For Elastic Metal, check out our documentation on configuring the network interface.
You can configure:
- Up to 8 Private Networks per Scaleway resource
- Up to 255 Private Networks per Organization
- Up to 512 Scaleway resources per Private Network
No, Private Network interfaces will appear on your resources without any reboot.
Yes, you can configure IPv6 within Private Networks. To use it, the netmask should always be
/64 and we recommend to use
fc00::/7 unique local address (ULA) range. ULA IPv6 address generators are widely available to generate a personalized range.
No, they do not require a public IPv4 address.
Yes. You can attach a Public Gateway to your Private Network and enable NAT to provide Internet access to your Instances, Elastic Metal servers and other Scaleway resources.
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 by reaching us on the Scaleway Community Slack.
Yes. You can attach a Public Gateway to your Private Network and enable DHCP to provide IP autoconfiguration for your resources.