Skip to content

Commit ff9528d

Browse files
committed
fix(vpc): finish default stuff
1 parent 78f2920 commit ff9528d

File tree

5 files changed

+5
-5
lines changed

5 files changed

+5
-5
lines changed

pages/elastic-metal/how-to/use-private-networks.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ You can also attach custom resources, such as virtual machines hosted on your El
6565
- Select **Attach to a new Private Network**, and enter a name for the new Private Network you wish to create.
6666
<Message type="note">
6767
The Private Network will have default settings, meaning:
68-
- It is created in your [default VPC](/vpc/concepts/#default-vpc) for the region. If you do not have a default VPC, you must create a VPC first, before creating a Private Network.
68+
- 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
6969
- 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.
7070
</Message>
7171
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.

pages/instances/how-to/use-private-networks.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ If you want to create a Private Network without immediately attaching any resour
3737
6. Enter a **Name** for your Private Network, or leave the randomly-generated name in place.
3838
7. Click **Attach to a Private Network** to finish.
3939

40-
Your Private Network is created in your [default VPC](/vpc/concepts/#default-vpc) for the region, if one exists. The Private Network will have default settings, meaning an auto-generated [CIDR block](/vpc/concepts/#cidr-block).
40+
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).
4141

4242
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).
4343

pages/vpc/concepts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ An IPv4 CIDR block and an IPv6 CIDR block are defined for each Scaleway Private
2626

2727
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.
2828

29-
If you created your Scaleway Project after 13 May 2025, default VPCs are no longer auto-created for you, and the concept of a default VPC no longer exists. You must explicitly create a VPC before you can create a Private Network.
29+
If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for you, and the concept of a default VPC no longer exists.
3030

3131
## DHCP
3232

pages/vpc/faq.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ You cannot delete a default VPC, but you can rename it, and/or create other VPCs
2828
Default VPCs do not prevent you from deleting an otherwise empty Project.
2929
</Message>
3030

31-
If you created your Scaleway Project after 13 May 2025, default VPCs are no longer auto-created for you, and the concept of a default VPC no longer exists. You must explicitly create a VPC before you can create a Private Network.
31+
If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for the Project, and the concept of a default VPC no longer exists. If you try to create a Private Network without having an existing VPC for the appropriate region, will a VPC will be auto-created for you, but the default label does not apply.
3232

3333
## VPC routing
3434

pages/vpc/how-to/create-vpc.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ It is currently not possible to change the default VPC for a region, nor to dele
4242

4343
### After 13 May 2025
4444

45-
If you created your Scaleway Project after 13 May 2025, default VPCs are no longer auto-created for you, and the concept of a default VPC no longer exists. You must explicitly create a VPC before you can create a Private Network.
45+
If you created your Scaleway Project after 13 May 2025, default VPCs are no longer auto-created for you, and the concept of a default VPC no longer exists.
4646

4747
## How to create a VPC
4848

0 commit comments

Comments
 (0)