---
title: How to use Private Networks with your Serverless Containers
description: This page explains how to use Private Networks for Scaleway Serverless Containers
tags: private-networks private networks instance containers vpc
dates:
  validation: 2025-06-25
  posted: 2021-06-25
---
import Requirements from '@macros/iam/requirements.mdx'
import VPCRoutingCompatibility from '@macros/vpc/vpc-routing-compatibility.mdx'

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

For full information about Scaleway Private Networks and VPC, see our [dedicated documentation](/vpc/) and [best practices guide](/vpc/reference-content/getting-most-private-networks/).

<VPCRoutingCompatibility />

<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
- [Created a Private Network](/vpc/how-to/create-private-network/)


## How to create a Private Network

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

## How to attach a Serverless Container to a Private Network

<Tabs>
  <TabsTab label="Existing container">
  1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays.
  2. Click the relevant containers namespace.
  3. Click the name of the container you want to manage.
  4. Open the **Settings** tab, then scroll to the **Advanced options** section.
  5. In the **Private Networks** tab, select a Private Network from the dropdown menu.
  6. Click **Save container settings**.

  Your container is redeployed, and is now attached to the selected Private Network.
</TabsTab>
<TabsTab label="New container">
  1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays.
  2. Click the **containers namespace** in which you want to create your container.
  3. Click **+ Create container**. The container creation wizard displays.
  4. Scroll to the **Advanced options** section.
  5. In the **Private Networks** tab, select a Private Network from the dropdown menu.
  6. Configure the other parameters of your container, then click **Create container**. Refer to the [How to create a container](/serverless-containers/how-to/build-push-container-image/) for more information.

  Your new container is deployed, and is attached to the selected Private Network.
  </TabsTab>
</Tabs>

## How to detach a container from a Private Network

1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays.
2. Click the relevant containers namespace.
3. Click the name of the container you want to manage.
4. Open the **Settings** tab, then scroll to the **Advanced options** section.
5. In the **Private Networks** tab, click the <Icon name="unlink" /> icon next to the Private Network attached to your container.
6. Click **Save container settings**.

Your container is redeployed and is now detached from the Private Network.

## 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 Private Networks section of the console. Follow the procedure detailed in our [dedicated Private Networks documentation](/vpc/how-to/delete-private-network/).

## Private Networks and containers limitations

For more information on limitations when using Private Networks with Serverless Containers, refer to the [dedicated documentation](/serverless-containers/reference-content/containers-private-networks).