---
title: How to use Private Networks with your Instances
description: This page explains how to use Private Networks for Scaleway Instances
tags: private-networks private networks instance
dates:
  validation: 2025-12-18
  posted: 2021-05-26
---
import Requirements from '@macros/iam/requirements.mdx'


[Private Networks](/vpc/concepts/#private-networks) allow your Instances to communicate in an isolated and secure network without needing to be connected to the public internet. Each Instance can be connected to one or several Private Networks, letting you build your own network topologies.

Private Networks are LAN-like layer 2 ethernet networks. A new network interface with a unique media access control address (MAC address) is configured on each Instance in a Private Network. Private Networks' built-in DHCP server manages the distribution of private IP addresses for Instances (and other resources) when they are attached to the network.

<Requirements />

- A Scaleway account logged into the [console](https://console.scaleway.com)
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
- An [Instance](/instances/how-to/create-an-instance/)

## How to create a new Private Network

The procedure below shows you how to create a new Private Network to attach to an existing Instance. The Private Network will have default settings, with an auto-generated [CIDR block](/vpc/concepts/#cidr-block). This CIDR block will be used to allocate private IP addresses to Instances attached to the network. Each Instance will get an IPv4 and an IPv6 address on the Private Network.

If you want to create a Private Network without immediately attaching any resources or create it in a specific VPC or with a custom CIDR block, follow [this procedure instead](/vpc/how-to/create-private-network/).

1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
2. Select the Availability Zone (AZ) from the drop-down menu (e.g., `PAR1`) to view resources in the selected AZ.
3. Click the Instance you want to add a Private Network to.
4. Click the **Private Networks** tab.
5. Click the **Attach to a Private Network** button. A pop-up displays.
6. Click the **Select a Private Network** drop-down, then click **Create a new Private Network**.
7. Enter a **Name** for your Private Network, or leave the randomly-generated name in place. Optionally, you can also enter tags.
8. Select the VPC to create the Private Network in.
9. Click **Attach to a Private Network** to finish.

The Private Network will have default settings, meaning an auto-generated [CIDR block](/vpc/concepts/#cidr-block).

You are taken back to the Private Networks tab, where your new Private Network is now displayed in the list and you can see the IP address for your Instance on the network. For more information about resources' private IP addresses on a Private Network, see our [dedicated documentation](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address).

## How to attach Instances to an existing Private Network

1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
2. Select the Availability Zone (AZ) from the drop-down menu (e.g., `PAR1`) to view resources in the selected AZ.
3. Click the Instance you want to add a Private Network to.
4. Click the **Private Networks** tab.
5. Click the **Attach to a Private Network** button. A pop-up displays.
6. Select the existing Private Network you want to attach the Instance to from the drop-down list.
    <Message type="note">
      Only Instances from the same region as your Private Network will be available in the drop-down menu.
    </Message>
7. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/ipam/concepts/#reserved-ip-address)** for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Instance will have on this Private Network.
8. Click **Attach to Private Network**.

    You are taken back to the **Private Networks** tab, where you can see the private IP address for the Instance you just attached. For more information about resources' private IP addresses on a Private Network, see our [dedicated documentation](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address).

## How to detach Instances from a Private Network

1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
2. Select the Availability Zone (AZ) from the drop-down menu (e.g., `PAR1`) to view resources in the selected AZ.
3. Click the Instance you want to detach from a Private Network.
4. Click the **Private Networks** tab.
5. Click the <Icon name="unlink" /> icon next to the resource you want to detach.
6. Click **Detach resource** when prompted to confirm.

    You are taken back to the **Private Networks** tab, where the Instance you just detached is now removed from the list.

## How to delete a Private Network

<Message type="note">
  Before deleting a Private Network, you must [detach](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) all resources attached to it.
</Message>

This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/delete-private-network/).