fix(vpc): update default vpc info (#4920)

RoRoJ · web-flow · commit eb2bc032ee81 · 2025-05-13T09:39:48.000+02:00
* fix(vpc): update default vpc

* fix(vpc): finish default stuff

* fix(vpc): corrections

* fix(pgw): fix
diff --git a/pages/elastic-metal/how-to/use-private-networks.mdx b/pages/elastic-metal/how-to/use-private-networks.mdx
@@ -65,7 +65,7 @@ You can also attach custom resources, such as virtual machines hosted on your El
     - Select **Attach to a new Private Network**, and enter a name for the new Private Network you wish to create.
     <Message type="note">
     The Private Network will have default settings, meaning:
-      - It is created in your [default VPC](/vpc/concepts/#default-vpc) for the region
+      - It is created in your [default VPC](/vpc/concepts/#default-vpc) for the region. If you do not have an existing VPC for the appropriate region, one will be auto-created for you
       - It has an auto-generated [CIDR block](/vpc/concepts/#cidr-block) used to allocate private IP addresses to servers attached to the network. Each attached Elastic Metal server will get an IPv4 and an IPv6 address on the Private Network.
     </Message>
 6. 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 Elastic Metal server will have on this Private Network.
diff --git a/pages/instances/how-to/use-private-networks.mdx b/pages/instances/how-to/use-private-networks.mdx
@@ -25,7 +25,7 @@ Private Networks are LAN-like layer 2 ethernet networks. A new network interface
 
 ## 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 (created in your [default VPC](/vpc/concepts/#default-vpc) for the region, 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.
+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/).
 
@@ -37,7 +37,7 @@ If you want to create a Private Network without immediately attaching any resour
 6. Enter a **Name** for your Private Network, or leave the randomly-generated name in place.
 7. Click **Attach to a Private Network** to finish.
 
-    Your Private Network is created in your [default VPC](/vpc/concepts/#default-vpc) for the region. The Private Network will have default settings, meaning an auto-generated [CIDR block](/vpc/concepts/#cidr-block).
+    Your Private Network is created in your [default VPC](/vpc/concepts/#default-vpc) for the region, if one exists. If you do not have an existing VPC for the appropriate region, one will be auto-created for you. 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).
 
diff --git a/pages/public-gateways/how-to/configure-a-public-gateway.mdx b/pages/public-gateways/how-to/configure-a-public-gateway.mdx
@@ -36,7 +36,7 @@ This page shows you how to attach a [Public Gateway](/public-gateways/concepts/#
       <Message type="note">
         Only Private Networks which are in the same region as the Public Gateway are displayed in this list.
       </Message>
-    - If you want to create and attach a new Private Network, select **Attach to a new Private Network**. The Private Network will be created with default configuration (a [CIDR block](/vpc/concepts#cidr-block) will be automatically defined), in your default VPC for the region. A name for the Private Network will be suggested for you, but feel free to overwrite this with a new name of your choice. Dynamic NAT will be automatically activated on the Public Gateway for the Private Network.
+    - If you want to create and attach a new Private Network, select **Attach to a new Private Network**. The Private Network will be created with default configuration (a [CIDR block](/vpc/concepts#cidr-block) will be automatically defined), in your default VPC for the region, if one exists. If you do not have an existing VPC for the appropriate region, one will be auto-created for you. A name for the Private Network will be suggested, but feel free to overwrite this with a new name of your choice. Dynamic NAT will be automatically activated on the Public Gateway for the Private Network.
 6. 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.
 7. Use the toggle to select whether to **Advertise the default route**. Find out more about this setting in our [concepts documentation](/public-gateways/concepts/#default-route).
 8. Click **Attach to Private Network** to finish. You are taken back to the Private Networks tab, where the network you attached now appears, along with the services configured and the IP address of the Public Gateway.
diff --git a/pages/vpc/concepts.mdx b/pages/vpc/concepts.mdx
@@ -9,7 +9,7 @@ tags: network vpc virtual-private-cloud regional private network routing
 categories:
   - network
 dates:
-  validation: 2024-12-03
+  validation: 2025-05-05
   posted: 2023-02-06
 ---
 
@@ -24,7 +24,9 @@ An IPv4 CIDR block and an IPv6 CIDR block are defined for each Scaleway Private
 
 ## Default VPC
 
-Scaleway currently has three regions: Paris, Amsterdam and Warsaw. One default VPC is automatically created for each region, in each Scaleway [Project](/organizations-and-projects/concepts/#project). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC.
+If you created your Scaleway [Project](/organizations-and-projects/concepts/#project) before 13 May 2025, one **default VPC** was automatically created in it for each region (Paris, Amsterdam and Warsaw). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC.
+
+If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for you. The first VPC that you create in each region is designated as its default VPC.
 
 ## DHCP
 
@@ -119,7 +121,7 @@ A vRouter is a virtualized router that sits inside a VPC and manages layer 3 rou
 
 ## VPC
 
-VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. Within each VPC, you can create **Private Networks** and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region. One default VPC for every available region is automatically created in each Scaleway [Project](/organizations-and-projects/concepts/#project).
+VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. Within each VPC, you can create **Private Networks** and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region.
 
 <Lightbox src="scaleway-vpc-pn-diag.webp" alt="A diagram shows that several Private Networks exist within a single VPC" size="small"/>
 
diff --git a/pages/vpc/faq.mdx b/pages/vpc/faq.mdx
@@ -5,7 +5,7 @@ meta:
 content:
   h1: VPC FAQ
 dates:
-  validation: 2024-12-16
+  validation: 2025-05-05
 category: network
 productIcon: VpcProductIcon
 ---
@@ -14,24 +14,22 @@ productIcon: VpcProductIcon
 
 ### What is the difference between VPC and a Private Network?
 
-One default VPC (**V**irtual **P**rivate **C**loud) for every available region is automatically created in each Scaleway [Project](/organizations-and-projects/concepts/#project). A VPC offers layer 3 network isolation.
-
-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. Resources attached to a Private Network can then communicate between themselves in an isolated and secure layer 2 network, away from the public internet. VPC routing facilitates communication between resources on the different Private Networks within the VPC.
+A VPC offers layer 3 network isolation. Within each VPC, you can create multiple **Private Networks** (layer 2) and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region. Resources attached to a Private Network can then communicate between themselves in an isolated and secure network, away from the public internet. VPC routing facilitates communication between resources on the different Private Networks within the VPC.
 
 <Lightbox src="scaleway-vpc-pn-diag.webp" alt="A diagram shows that several Private Networks exist within a single VPC" size="small"/>
 
-In the future, VPC will allow you to interconnect your VPC with other networks, define access control lists and more.
-
 ### What is a default VPC and why can I not delete it?
 
-Scaleway currently has three regions: Paris, Amsterdam and Warsaw. One default VPC is automatically created for each region, in each Scaleway [Project](/organizations-and-projects/concepts/#project). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC.
+If you created your Scaleway [Project](/organizations-and-projects/concepts/#project) before 13 May 2025, one **default VPC** was automatically created in it for each region (Paris, Amsterdam and Warsaw). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC.
 
-You cannot delete a default VPC, but you can rename it, and/or create other VPCs and use those rather than the default VPCs, if you prefer. 
+You cannot delete a default VPC, but you can rename it, and/or create other VPCs and use those rather than the default VPCs, if you prefer. Watch this space for upcoming functionality to delete default VPCs.
 
 <Message type="note">
 Default VPCs do not prevent you from deleting an otherwise empty Project.
 </Message>
 
+If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for the Project. The first VPC that you create in each region is designated as its default VPC. If you try to create a Private Network without having an existing VPC for the appropriate region, a VPC will be auto-created for you.
+
 ## VPC routing
 
 ### Can I route traffic between different Private Networks on the same VPC?
diff --git a/pages/vpc/how-to/create-private-network.mdx b/pages/vpc/how-to/create-private-network.mdx
@@ -28,9 +28,7 @@ While DHCP is built into all new Private Networks, it may not be automatically a
 
 ## How to create a Private Network
 
-1. Click **VPC** in the **Network** section of the side menu. The list of your VPCs displays:
-
-    Each Private Network must be created within a VPC. A default VPC is created for you in each Scaleway region.
+1. Click **VPC** in the **Network** section of the side menu. The list of your VPCs displays. Each Private Network must be created within a VPC.
 
 2. Click the VPC you wish to create your Private Network in.
 
diff --git a/pages/vpc/how-to/create-vpc.mdx b/pages/vpc/how-to/create-vpc.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to create a Virtual Private Cloud (VPC) with the Scaleway console. Follow this detailed guide to set up secure and isolated network infrastructure for your cloud resources.
 tags: vpc default create regional virtual-private-cloud
 dates:
-  validation: 2025-01-04
+  validation: 2025-05-05
   posted: 2023-06-13
 categories:
   - network
@@ -22,7 +22,9 @@ VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Sca
 
 ## How to identify your default VPCs
 
-One default VPC per region is automatically created per Scaleway [Project](/organizations-and-projects/concepts/#project).
+### Before 13 May 2025
+
+If you created your Scaleway [Project](/organizations-and-projects/concepts/#project) before 13 May 2025, one **default VPC** was automatically created in it for each region (Paris, Amsterdam and Warsaw). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC.
 
 Click **VPC** in the **Network** section of the Scaleway console side menu. Your VPC [dashboard](https://console.scaleway.com/vpc/vpc) displays:
 
@@ -36,7 +38,11 @@ You see three default VPCs (each with a **DEFAULT** badge next to it), one for e
 
 Each of these VPCs is named `default` (though you can [edit](#how-to-edit-a-vpcs-name-and-tags) the name if you wish). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC.
 
-It is currently not possible to change the default VPC for a region.
+It is currently not possible to change the default VPC for a region, nor to delete a VPC.
+
+### After 13 May 2025
+
+If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for you. The first VPC that you create in each region is designated as its default VPC.
 
 ## How to create a VPC
 
diff --git a/pages/vpc/quickstart.mdx b/pages/vpc/quickstart.mdx
@@ -7,15 +7,13 @@ content:
   paragraph: This page shows you how to get started with Scaleway Virtual Private Cloud (VPC).
 tags: vpc virtual-private-cloud regional private network dhcp private-ip
 dates:
-  validation: 2025-04-24
+  validation: 2025-05-05
   posted: 2022-02-06
 categories:
   - network
 ---
 
-VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. 
-
-One **default VPC** per region is automatically created per Scaleway [Project](/organizations-and-projects/concepts/#project), and you can create more VPCs if you wish. 
+VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. You can create one or more VPCs in each Scaleway [region](/vpc/concepts/#region-and-availability-zone).
 
 Within each VPC, you can create **Private Networks** and attach Scaleway resources (Instances, Elastic Metal servers, Load Balancers etc.) to them, as long as the resources are within the network's region. Resources attached to a Private Network can communicate between themselves in an isolated and secure virtual layer 2 network, away from the public internet. 
 
@@ -35,25 +33,11 @@ If you are looking for detailed guidance on constructing your private infrastruc
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 
-## How to identify your default VPCs
-
-One default VPC per region is automatically created per Scaleway [Project](/organizations-and-projects/concepts/#project). You can [create more](/vpc/how-to/create-vpc/) if you wish, but it is not necessary for basic use cases.
-
-Click **VPC** in the **Network** section of the Scaleway console side menu. Your [VPC dashboard](https://console.scaleway.com/vpc/vpc) displays:
-
-    <Lightbox src="scaleway-default-vpc.webp" alt="" />
-
-You see three default VPCs, one for each of the following regions:
-
-- Paris `PAR`
-- Amsterdam `AMS`
-- Warsaw `WAW`
-
-Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by [creating](#how-to-create-a-vpc) and specifying a different VPC.
-
 ## How to create a VPC
 
-If you want to create more VPCs beyond the default ones created for you, you can do so via the following steps:
+<Message type="tip">
+If you created your Scaleway [Project](/organizations-and-projects/concepts/#project) before 13 May 2025, one **default VPC** was automatically created in it for each region (Paris, Amsterdam and Warsaw). [Find out more](/vpc/faq/#what-is-a-default-vpc-and-why-can-i-not-delete-it). 
+</Message>
 
 1. Click **VPC** in the **Network** section of the Scaleway console side menu.
 
diff --git a/pages/vpc/reference-content/getting-most-private-networks.mdx b/pages/vpc/reference-content/getting-most-private-networks.mdx
@@ -31,7 +31,7 @@ VPCs and Private Networks are both **regional** resources. When you create a Pri
 | Netherlands - Amsterdam | AMS1, AMS2, AMS3          |
 | Poland - Warsaw         | WAW1, WAW2, WAW3          |
 
-One default VPC for each region is automatically created in each Scaleway [Project](/organizations-and-projects/concepts/#project). The [**VPC routing**](/vpc/concepts/#routing) feature allows for managed and custom routes between the Private Networks of a VPC, so resources on different Private Networks can communicate.
+The [**VPC routing**](/vpc/concepts/#routing) feature allows for managed and custom routes between the Private Networks of a VPC, so resources on different Private Networks can communicate.
 
 <Lightbox src="scaleway-routing-diag.webp" alt="A diagram shows two Private Networks inside a VPC. A route table on a virtual router sits inside the VPC, and the route table is synchronized to each resource attached to the VPC's Private Networks. An Instance on Private Network A is able to send a packet to an Instance on Private Network B. An Elastic Metal server on Private Network A is able to send a packet to the public internet via the Public Gateway also on Private Network A." />
 
diff --git a/pages/vpc/reference-content/use-case-basic.mdx b/pages/vpc/reference-content/use-case-basic.mdx
@@ -74,7 +74,7 @@ This kind of infrastructure is appropriate for many applications, including but
 
 Follow the steps below to create this infrastructure using the [Scaleway console](https://console.scaleway.com/organization):
 
-1. [Create a VPC](/vpc/how-to/create-vpc/) (or use the [default VPC](/vpc/how-to/create-vpc/#how-to-identify-your-default-vpcs) pre-created for each Scaleway Project in the appropriate [region](/vpc/concepts/#region-and-availability-zone)).
+1. [Create a VPC](/vpc/how-to/create-vpc/) (or use a [default VPC](/vpc/how-to/create-vpc/#how-to-identify-your-default-vpcs) in the appropriate [region](/vpc/concepts/#region-and-availability-zone)).
 2. [Create a Private Network](/vpc/how-to/create-private-network/) inside the VPC. You can either let Scaleway create the network with an auto-generated subnet, which will provide the private IP addresses for attached resources, or specify a self-defined subnet.
 3. [Create a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) (set it to advertise the [default route](/public-gateways/concepts/#default-route)) and [attach it to the Private Network](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network).
 4. [Set up SSH bastion](/public-gateways/how-to/use-ssh-bastion/) on the Public Gateway, to allow administrator access.
diff --git a/pages/vpc/troubleshooting/cant-delete-vpc-pn.mdx b/pages/vpc/troubleshooting/cant-delete-vpc-pn.mdx
@@ -49,7 +49,7 @@ The VPC must contain no Private Networks before you can delete it.
 
 In order to successfully delete a Private Network, you must ensure no resources are attached to it, and there are no private IPs reserved within the network. See the [information below](#i-cant-delete-my-private-network) for full details.
 
-**Ensure you are not trying to delete a default VPC**. Each Scaleway Project has three auto-created default VPCs, one for each region. These VPCs cannot be deleted. They are free of charge. The existence of default VPCs does not block the deletion of a Scaleway account or Project, as long as the default VPCs do not contain Private Networks with associated/attached resources.
+**Ensure you are not trying to delete a default VPC**. Each Scaleway Project created before 13 May 2025 has three auto-created default VPCs, one for each region. These VPCs cannot be deleted. They are free of charge. The existence of default VPCs does not block the deletion of a Scaleway account or Project, as long as the default VPCs do not contain Private Networks with associated/attached resources.
 
     You can identify default VPCs by the **Default** badge in the VPC listing, even if you have changed the name of the VPC itself.
 
