fix(vpc): new custom resource attachment

Author: RoRoJ

faq/vpc.mdx

@@ -0,0 +1,43 @@
+---
+meta:
+  title: VPC FAQ
+  description: Discover Scaleway VPC and Private Networks.
+content:
+  h1: VPC
+dates:
+  validation: 2024-12-16
+category: network
+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. Attached resources can then communicate between themselves in an isolated and secure layer 2 network, away from the public internet.
+
+In the future, VPC will allow you to interconnect your VPC with other networks, define access control lists and more.
+
+## Can I route traffic between different Private Networks on the same VPC?
+
+Yes, [VPC routing](/vpc/concepts#routing) allows you to automize the routing of traffic between resources in different Private Networks within the same VPC.
+
+## Can I route traffic between different Private Networks in different VPCs or different Scaleway Projects?
+
+This is not currently possible. You may consider using a VPN tunnel to achieve this, for example [IPsec](https://en.wikipedia.org/wiki/IPsec) or [WireGuard](https://en.wikipedia.org/wiki/WireGuard). Scaleway also offers an [OpenVPN InstantApp](/tutorials/openvpn-instant-app/), making it easy to install a VPN directly on an Instance.
+
+## What happened to my classic, mono-AZ Private Network?
+
+When VPC and regional Private Networks moved from Public Beta to General Availability, all mono-AZ Private Networks were automatically migrated to be regional. [Read the documentation](/vpc/reference-content/vpc-migration/) to find out more about the migration process.
+
+## Do resources' IP addresses on a Private Network risk changing when allocated by managed DHCP?
+
+With managed DHCP, the IP is allocated when the resource is attached to a Private Network, and released only when the resource is detached or deleted. The IP address remains stable across reboots and long power offs, and will not change except upon deletion or detachment from the Private Network.
+
+Nonetheless, you can also reserve specific IPs from a Private Network's CIDR block, and use these IPs to attach specific resources, if you prefer. See our documentation on [how to reserve IPs](/ipam/how-to/reserve-ip/).
+
+## How can I manage IP addresses for my Proxmox Virtual Machines (VMs) on Elastic Metal servers?
+
+For this purpose use the option of attaching a **custom resource** to a Private Network, specifying its MAC address. Full instructions for attaching custom resources are in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn#how-can-i-manage-ip-addresses-for-my-proxmox-virtual-machines-vms-on-elastic-metal-servers).
+
+You can also [reserve a private IP address](/ipam/how-to/reserve-ip/) with IPAM, and use this reserved address to attach a custom resource.

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

@@ -52,7 +52,7 @@ You can choose to enable the Private Networks feature during the [creation of yo
 
 You can attach/detach Elastic Metal servers to a Private Network from either the Elastic Metal section of the console, or the VPC section.
 
-You can also reserve IP addresses with IPAM and attach them to specific MAC addresses, to facilitate the attachment of virtual machines hosted on your server, to Private Networks. See the IPAM documentation on [reserving a private IP with an attached MAC address](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address) for more information.
+You can also attach custom resources, such as virtual machines hosted on your Elastic Metal server, to Private Networks, by specifying their MAC addresses upon attachment/ Follow the instructions for attaching such a resource in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn/).
 
 ### From the Elastic Metal section of the console
 

pages/ipam/faq.mdx

@@ -26,4 +26,4 @@ Currently, the Scaleway console only supports attachment with a reserved IP for
 
 ## Can I use a reserved private IP with a virtual machine hosted on my Elastic Metal server?
 
-Yes, this functionality is now available via the Scaleway console and API. See [how to reserve a private IP address with an attached MAC address](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address).
+Yes, this functionality is now available via the Scaleway console and API. Simply reserve an IP with IPAM, then select it when [attaching a custom resource to a Private Network](/vpc/how-to/attach-resources-to-pn/).

pages/ipam/how-to/reserve-ip.mdx

@@ -31,6 +31,8 @@ This page sets out the steps necessary to reserve an IP address with IPAM.
 
 ## How to reserve a private IP address
 
+The procedure is the same, whether you want to use the IP to attach a Scaleway-managed resource (Instance, Elastic Metal server etc.), or a custom resource (such as a VM hosted on an Elastic Metal server).
+
 1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
 
 2. Click **Reserve private IP**. The following screen displays:
@@ -50,37 +52,11 @@ This page sets out the steps necessary to reserve an IP address with IPAM.
     Four IP addresses from each CIDR block are unavailable for reservation: the first two and last two in the block. For example, for the subnet `172.16.12.0/22` the following addresses cannot be reserved or assigned to any resource: `172.16.12.0`, `172.16.12.1`, `172.16.15.254` and `172.16.15.255`.
     </Message>
 
-5. Define whether you want to attach a MAC address to the reserved IP. **Only do this for custom resources** e.g. virtual machines hosted on a Proxmox cluster on an Elastic Metal server. 
-
-    <Message type="important">
-    Do **not** attach a MAC address for reserved IPs you want to use with standard Scaleway resources such as Instances, Load Balancers or Elastic Metal servers themselves.
-    </Message>
-
-    For more help with attaching MAC addresses, [see below](#how-to-reserve-a-private-ip-address-with-an-attached-mac-address).
-
-6. Click **Reserve** to reserve the IP.
+5. Click **Reserve** to reserve the IP.
 
     The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](#how-to-release-a-reserved-private-ip-address) it.
 
-## How to reserve a private IP address with an attached MAC address
-
-When you reserve a private IP, you have the option to attach a MAC address to it. This allows you to use the IP with a custom resource e.g. virtual machines hosted on a Proxmox cluster on an Elastic Metal server. This functionality marks the final stage of replacing the now-deprecated static DHCP reservations via the Public Gateway.
-
-It is only possible to attach a MAC address during the IP reservation. You cannot edit an existing reserved IP to attach a MAC address.
-
-1. Follow the steps above to [reserve a private IP](#how-to-reserve-a-private-ip-address), and at step 5, check the box to attach a MAC address.
-
-2. Enter the MAC address of the custom resource you want to attach, e.g. `00:1B:44:11:3A:B7`.
-
-3. Enter the name of the resource. This will be used for DNS resolution on the Private Network.
-
-4. Click **Reserve**.
-
-    The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. 
-    
-    If you later attach this reserved IP address to a standard Scaleway resource e.g. an Instance, the attached MAC address and resource name will be erased.
-
-## How to attach a resource to a Private Network using a reserved IP address
+## How to attach a managed resource to a Private Network using a reserved IP address
 
 You can currently attach **Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** to Private Networks using a reserved IP address. Support for Managed Databases will be coming soon.
 
@@ -92,6 +68,12 @@ The option to use a reserved IP displays when you attach the resource to a Priva
 - Attach a Load Balancer to a Private Network from the [Load Balancer](/load-balancer/how-to/use-with-private-network/) product dashboard
 - Attach a Public Gateway to a Private Network from the [Public Gateways](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) product dashboard
 
+## How to attach a custom resource to a Private Network using a reserved IP address
+
+You can use reserved IP addresses to attach custom resources, such as VMs hosted on Elastic Metal servers, to Scaleway Private Networks. In doing so, you are prompted to specify the MAC address of the custom resource.
+
+Attach the custom resource from the Private Network's dashboard in the Scaleway console, by follow the procedure detailed in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn/).
+
 ## How to release a reserved private IP address
 
 You can release a reserved IP address, as long as it is not attached to a resource. Releasing the IP means it goes back into the general pool of available IP addresses for that Private Network, and could potentially be auto-allocated to a new resource joining the network.

pages/ipam/quickstart.mdx

@@ -61,6 +61,8 @@ You can currently use IPAM in the Scaleway console to list the [private IP addre
 
 ## How to reserve a private IP address
 
+The procedure is the same, whether you want to use the IP to attach a Scaleway-managed resource (Instance, Elastic Metal server etc.), or a custom resource (such as a VM hosted on an Elastic Metal server).
+
 1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
 
 2. Click **Reserve private IP**. The following screen displays:
@@ -80,4 +82,6 @@ You can currently use IPAM in the Scaleway console to list the [private IP addre
     Four IP addresses from each CIDR block are unavailable for reservation: the first two and last two in the block. For example, for the subnet `172.16.12.0/22` the following addresses cannot be reserved or assigned to any resource: `172.16.12.0`, `172.16.12.1`, `172.16.15.254` and `172.16.15.255`.
     </Message>
 
-    The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](/ipam/how-to/reserve-ip/#how-to-release-a-reserved-private-ip-address) it.
+5. Click **Reserve** to reserve the IP.
+
+    The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](#how-to-release-a-reserved-private-ip-address) it.

pages/ipam/reference-content/ipv6.mdx

@@ -71,7 +71,7 @@ In addition to the possibility of attaching and detaching flexible IP addresses,
 
 When you attach an Elastic Metal server to a Private Network, it gets both an IPv4 and an IPv6 address on that network.  You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use.
 
-You can also use IPAM's [reserve a private IP](https://www.scaleway.com/en/developers/api/ipam/#path-ips-reserve-a-new-ip) and [attach IP to custom resource](https://www.scaleway.com/en/developers/api/ipam/#path-ips-attach-ip-to-custom-resource) feature to attach an IPv6 address to a named resource via its MAC address. This is suitable for ensuring virtual machines on your Elastic Metal server get private IPv6 addresses.
+To attach resources such as virtual machines hosted Elastic Metal servers to Private Networks, use the [attach custom resource](/vpc/how-to/attach-resources-to-pn/) feature, specifying the MAC address of the custom resource. This is suitable for ensuring virtual machines on your Elastic Metal server get private IPv6 addresses.
 
 #### Going further