VPC allows you to build your own Virtual Private Cloud on top of Scaleway’s shared public cloud. Within each VPC, you can create multiple Private Networks and attach Scaleway resources to them, as long as the resources are in an AZ within the network’s region. Attached resources can then communicate between themselves in an isolated and secure layer 2 network, away from the public internet.
Private Networks also have built-in Dynamic Host Configuration Protocol (DHCP), making it easy to manage the private IP addresses of your resources on the network.
Up to 512 resources can be attached to each Private Network, and each resource can be attached to up to eight Private Networks.
The following resource types can be attached to a Private Network:
Scaleway-managed resources:
Kubernetes Kapsule clusters and Managed Databases for Redis™ are also compatible with Private Networks, but they can only be attached to a Private Network at the time of creating the resource. It is not possible to attach a cluster or Redis™ database to a Private Network after its creation, or change the attached Private Network.
Custom resources
To complete the actions presented below, you must have:
Click VPC in the Network section of the side menu. Your VPC dashboard displays:
Click the VPC containing the Private Network to which you want to attach a resource.
A list of Private Networks in this VPC displays:
Click the Private Network to which you want to attach a resource.
The Private Network’s dashboard displays.
Click the Attached resources tab.
Use the toggle to select the type of resource you want to attach:
Click + Attach resource. A pop-up displays.
Complete the required information about the resource to attach. This depends on whether you are attaching a managed or custom resource.
Only Instances, Load Balancers, Public Gateways, and Elastic Metal servers are compatible with reserved IPs. Support for Managed Databases and Apple silicon will be coming soon. In the meantime, you must auto-allocate IPs for these products.
This method is intended for custom resources such as VMs hosted on Elastic Metal. Do not attempt to attach a managed resource, such as an Instance, via this method - use the Managed resource attachment instead.
00:1B:44:11:3A:B7.Click Attach to Private Network to finish.
You are returned to the list of attached resources, where the newly-attached resource now displays.
You can also attach a managed resource to a Private Network from the resource’s own section of the console. Follow the relevant steps below:
Note that for Kubernetes Kapsules and Managed Databases for Redis™, you can only attach the resource to a Private Network at the time of creating the resource itself.
For Elastic Metal servers and Apple silicon Mac minis, manual configuration of the network interface is required. This is not required for Instances or other types of managed resource. See the relevant documentation for Elastic Metal or Apple silicon for full instructions.
When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). Private IPs are assigned from the CIDR block defined at the time of the Private Network’s creation, either via auto-assignment or specification of a particular reserved IP.
No matter whether it is auto-allocated or pre-reserved, the IP remains stable for as long as the resource is attached to the Private Network, and does not risk changing even across reboots and long poweroffs. An auto-allocated IP is lost only when you delete the resource or detach it from the Private Network. Reserved IPs remain reserved even after you delete the resource or detach it from the Private Network, until you release the address.
You can view a resource’s IPv4 or v6 address in the Attached Resources tab of the Private Network itself (follow steps 1 - 5 above).
It can also be viewed via the Private Networks tab of the resource’s own dashboard.
When you attach a resource to a legacy Private Network on which you have not activated DHCP, no IP address is configured or shown on the screen shown above.
You will need to carry out manual configuration to set the IP address on the resource, or activate DHCP.
We strongly recommend that you activate DHCP on the Private Network to let us automatically handle IP address management.
If you do not see an IP address in the screens above for your resource, and you think you should, check out our troubleshooting guide.
In addition to using its IP address, you can also access a resource on a Private Network via its hostname, thanks to VPC’s inbuilt private DNS.
A resource’s hostname is equivalent to the name you gave the resource when creating it. For example, if you have an Instance with the name instance123 attached to a Private Network named prodpn, its address on that network is instance123.prodpn.internal. The .internal is important to allow Scaleway DNS to distinguish public and private hostnames.
For full information on Scaleway internal DNS and hostname formats, including troubleshooting advice, see our dedicated documentation.
Click VPC in the Network section of the side menu.
Click the VPC containing the Private Network from which you want to detach a resource.
A list of Private Networks in this VPC displays.
Click the Private Network from which you want to detach a resource.
Click the Attached resources tab.
The Private Network’s dashboard displays.
Click the Attached resources tab.
Use the toggle to select the type of resource you want to detach:
Click the «Unlink Icon» icon next to the resource you want to detach.
Click Detach resource when prompted to confirm.
You can also detach a managed resource to a Private Network from the resource’s own section of the console.