scaleway · RoRoJ · Dec 4, 2024 · Dec 3, 2024
@@ -1,13 +1,13 @@
 ---
 meta:
   title: IPAM - Concepts
-  description: This page explains all the concepts related to IPAM
+  description: Learn about IP Address Management (IPAM) concepts with Scaleway. Understand how to organize, allocate, and manage IP resources efficiently in your cloud infrastructure.
 content:
   h1: IPAM - Concepts
-  paragraph: This page explains all the concepts related to IPAM
+  paragraph: Learn about IP Address Management (IPAM) concepts with Scaleway. Understand how to organize, allocate, and manage IP resources efficiently in your cloud infrastructure.
 tags: ipam ip-address-management internet-protocol private-ip public-ip flexible-ip list-ips book-ip
 dates:
-  validation: 2024-05-30
+  validation: 2024-12-03
 categories:
   - networks
 ---
@@ -37,7 +37,7 @@ Scaleway resources may have a [public](#public-flexible-ip-address) IPv4 address
 
 Internet Protocol Version 6 is the most recent version of the IP protocol used for IP addresses. Each IPv6 address has 128 bits. Written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits, each group representing 16 bits and separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. This can also be notated as `2001:DB8::3:0:1FF:0:2E`.
 
-IPv6-compatible Scaleway resources may have a [public](#public-flexible-ip-address) IPv6 address (flexible IP) for accessibility from the public internet, and will have a [private](#private-ip-address) IPv6 address for each Private Network they are attached to. 
+IPv6-compatible Scaleway resources may have a [public](#public-flexible-ip-address) IPv6 address (flexible IP) for accessibility from the public internet, and will have a [private](#private-ip-address) IPv6 address for each Private Network they are attached to. [Find out more about IPv6 in the Scaleway ecosystem](/network/ipam/reference-content/ipv6/).
 
 ## Private IP address
 
@@ -51,7 +51,7 @@ Four IP addresses from each CIDR block are unavailable for reservation/use: the
 
 Public IP addresses identify devices on the public internet. You can enter the public IP address of an Instance into any browser connected to the Internet, and access content being served from that Instance. 
 
-Depending on the type of resource and its configuration, it may or may not have a public IP address. For example, you can choose to give an [Instance](/compute/instances/) one or more public IP addresses ([IPv4](#ipv4) and/or IPv6), or alternatively, no public IP address at all. Find out more about how to manage public connectivity in our [best practices guide](/network/ipam/reference-content/public-connectivity-best-practices/).
+Depending on the type of resource and its configuration, it may or may not have a public IP address. For example, you can choose to give an [Instance](/compute/instances/) one or more public IP addresses ([IPv4](#ipv4) and/or IPv6), or alternatively, no public IP address at all. Find out more about managing public connectivity in our [best practices guide](/network/ipam/reference-content/public-connectivity-best-practices/).
 
 Public IP addresses at Scaleway are often called flexible IP addresses, because you can move them between different resources. However, flexible IP addresses are scoped to a single product and to a single Availability Zone. If you create a flexible IP address for an Instance in `PAR-2`, you can move it to a different Instance in `PAR-2`, but not to an Instance in `PAR-1`, nor to an Elastic Metal server in any AZ.
 

@@ -1,13 +1,13 @@
 ---
 meta:
   title: How to manage frontends and backends
-  description: This page explains how to add frontends and backends
+  description: Learn how to manage frontends and backends with Scaleway Load Balancer. Configure endpoints, optimize traffic flow, and ensure seamless application performance.
 content:
   h1: How to manage frontends and backends
-  paragraph: This page explains how to add frontends and backends
+  paragraph: Learn how to manage frontends and backends with Scaleway Load Balancer. Configure endpoints, optimize traffic flow, and ensure seamless application performance.
 tags: load-balancer frontend backend
 dates:
-  validation: 2024-05-27
+  validation: 2024-12-03
   posted: 2021-05-26
 categories:
   - network

@@ -1,13 +1,13 @@
 ---
 meta:
   title: Load Balancers - Quickstart
-  description: This page shows you how to get started with Scaleway Load Balancers.
+  description: Get started with Scaleway Load Balancer in minutes. Follow this quickstart guide to set up, configure, and optimize traffic distribution for your applications.
 content:
   h1: Load Balancers - Quickstart
-  paragraph: This page shows you how to get started with Scaleway Load Balancers.
+  paragraph: TGet started with Scaleway Load Balancer in minutes. Follow this quickstart guide to set up, configure, and optimize traffic distribution for your applications.
 tags: load-balancer load balancer frontend backend
 dates:
-  validation: 2024-05-27
+  validation: 2024-12-03
   posted: 2021-05-26
 categories:
   - network
@@ -28,15 +28,7 @@ categories:
 
 3. Enter a **name** for your Load Balancer. Optionally, you can also add a **description** and assign **tags** to help organize your Load Balancers.
 
-4. Choose the **Availability Zone** in which your Load Balancer will be deployed geographically. Currently, we provide the following Availability Zones:
-      - `PAR1`: Paris 1, France.
-      - `PAR2`: Paris 2, France (innovative and sustainable Availability Zone).
-      - `AMS1`: Amsterdam, The Netherlands.
-      - `AMS2`: Amsterdam 2, The Netherlands.
-      - `AMS3`: Amsterdam 3, The Netherlands.
-      - `WAW1`: Warsaw, Poland.
-      - `WAW2`: Warsaw, Poland.
-      - `WAW3`: Warsaw, Poland.
+4. Choose the **Availability Zone** in which your Load Balancer will be deployed geographically.
 
 5. Select a Load Balancer **type**, according to your needs in terms of **bandwidth** and whether you want to be able to attach backend servers from other cloud providers than Scaleway (**Multi-cloud provider**).
 
@@ -92,6 +84,15 @@ Continue to the next section for configuring health checks.
 
 When you have finished configuring your frontend and backend, click **Create frontend and backend** at the bottom of the page to finish.
 
+## How to finish configuring your Load Balancer
+
+Depending on your use case, you may need to carry out further configuration on your Load Balancer. Refer to the following documentation:
+
+- [Add an SSL/TLS certificate](/network/load-balancer/how-to/add-certificate/), necessary for [SSL offloading or bridging](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/)
+- [Attach a Load Balancer to a Private Network](/network/load-balancer/how-to/use-with-private-network/)
+- Set up Load Balancer [ACLs](/network/load-balancer/how-to/create-manage-acls/) or [routes](/network/load-balancer/how-to/create-manage-routes/)
+- [Create an Edge Services pipeline](/network/load-balancer/how-to/use-edge-services/) for your Load Balancer
+
 ## How to delete a Load Balancer
 
 1. Click **Load Balancers** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Load Balancer dashboard displays.

@@ -1,15 +1,15 @@
 ---
 meta:
   title: VPC - Concepts
-  description: This page explains all the concepts related to VPC
+  description: Discover the key concepts of Scaleway Virtual Private Cloud (VPC). Learn how to isolate, secure, and manage your cloud resources effectively.
 content:
   h1: VPC - Concepts
-  paragraph: This page explains all the concepts related to VPC
-tags: network vpc virtual-private-cloud regional private network
+  paragraph: Discover the key concepts of Scaleway Virtual Private Cloud (VPC). Learn how to isolate, secure, and manage your cloud resources effectively.
+tags: network vpc virtual-private-cloud regional private network routing
 categories:
   - network
 dates:
-  validation: 2024-05-30
+  validation: 2024-12-03
   posted: 2023-02-06
 ---
 
@@ -30,9 +30,9 @@ Scaleway currently has three regions: Paris, Amsterdam and Warsaw. One default V
 
 **D**ynamic **H**ost **C**onfiguration **P**rotocol (DHCP) is a network management protocol for dynamically assigning IP addresses and other configuration parameters to devices in a Private Network.
 
-Managed DHCP was previously a feature of Scaleway's [Public Gateway](/network/public-gateways/concepts/#public-gateway), but is now built into Private Networks. A [CIDR block](#cidr-block) representing a range of available IP addresses is defined when creating the Private Network, and when you attach a resource to the network it is assigned a static, private IP address from this subnet. These IP addresses are managed by our internal [IPAM](#ipam), which acts a single source of truth and ensures full consistency. There is no need for users to manually assign private IP addresses to their resources as they join or leave the network.
+Managed DHCP was previously a feature of Scaleway's [Public Gateway](/network/public-gateways/concepts/#public-gateway), but is now built into Private Networks. A [CIDR block](#cidr-block) representing a range of available IP addresses is defined when creating the Private Network, and when you attach a resource to the network it is assigned a static, private IP address from this subnet. These IP addresses are managed by our internal [IPAM](#ipam), which acts a single source of truth and ensures full consistency. There is no need for users to manually assign private IP addresses to their resources as they join or leave the network. However, you can choose to assign particular [reserved IP addresses](/network/ipam/how-to/reserve-ip/) if you wish.
 
-With managed DHCP, a resource's IP address will never change as long as that resource is not detached from the Private Network. It remains stable across reboots and long poweroffs. The IP is allocated when the resource is attached, and released only when the resource is detached or deleted.
+Even with automatic IP address assignment, thanks to managed DHCP, a resource's IP address will never change as long as that resource is not detached from the Private Network. It remains stable across reboots and long poweroffs. The IP is allocated when the resource is attached, and released only when the resource is detached or deleted.
 
 The IPv4 address of Private Networks' DHCP server is `169.254.169.254`. The IPv6 address is `fe80:200:22ff:fe05:ca1e`.
 
@@ -56,13 +56,13 @@ Private Networks benefit from managed DNS, which resolves the hostnames of attac
 
 Internet Protocol Version 4 is the standard protocol used for IP addresses. Composed of 32 bits, when written in human-readable form an IPv4 address is generally shown as four octets separated by periods, e.g. `151.115.59.87`.
 
-When a resource is attached to a Private Network, it has a private IPv4 address on that network. Scaleway Private Networks' [DHCP](#dhcp) functionality assigns this private IPv4 address (as well as an IPv6 address, if the resource is IPv6-compatible) when the resource joins the network. [IPAM](/network/ipam/) allows you to list and manage your resources' private IP addresses.
+When a resource is attached to a Private Network, it has a private IPv4 address on that network. Scaleway Private Networks' [DHCP](#dhcp) functionality assigns this private IPv4 address (as well as an IPv6 address, if the resource is IPv6-compatible) when the resource joins the network. Alternatively you can reserve and attach an IP address of your choice with [IPAM](/network/ipam/how-to/reserve-ip/).
 
 ## IPv6
 
 Internet Protocol Version 6 is the most recent version of the IP protocol used for IP addresses. Composed of 128 bits, written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. This can also be notated as `2001:DB8::3:0:1FF:0:2E`.
 
-When an IPv6-compatible resource is attached to a Private Network, it has a private IPv6 address on that network. Scaleway Private Networks' [DHCP](#dhcp) functionality assigns this private IPv6 address when the resource joins the network. [IPAM](/network/ipam/) allows you to list and manage your resources' private IP addresses.
+When an IPv6-compatible resource is attached to a Private Network, it has a private IPv6 address on that network. Scaleway Private Networks' [DHCP](#dhcp) functionality assigns this private IPv6 address when the resource joins the network. Alternatively you can reserve and attach an IP address of your choice with [IPAM](/network/ipam/how-to/reserve-ip/).
 
 ## Private IP address
 

@@ -1,13 +1,13 @@
 ---
 meta:
   title: How to manage routing
-  description: This page explains how to manage routing in your Scaleway VPC
+  description: Learn how to manage routing in Scaleway Virtual Private Cloud (VPC). Configure custom routes to control traffic flow and optimize network performance.
 content:
   h1: How to manage routing
-  paragraph: This page explains how to manage routing in your Scaleway VPC
+  paragraph: Learn how to manage routing in Scaleway Virtual Private Cloud (VPC). Configure custom routes to control traffic flow and optimize network performance.
 tags: private-network vpc routing route-table routes default-route local-route subnet
 dates:
-  validation: 2024-05-28
+  validation: 2024-12-03
   posted: 2024-04-09
 categories:
   - network

@@ -1,13 +1,13 @@
 ---
 meta:
   title: Understanding VPC routing
-  description: This page provides detailed information about the VPC routing feature, which connects Private Networks within the same VPC.
+  description: Explore the fundamentals of VPC routing with Scaleway. Understand how to manage traffic flow and optimize network routes within your Virtual Private Cloud
 content:
   h1: Understanding VPC routing
-  paragraph: This page provides detailed information about the VPC routing feature, which connects Private Networks within the same VPC.
+  paragraph: Explore the fundamentals of VPC routing with Scaleway. Understand how to manage traffic flow and optimize network routes within your Virtual Private Cloud
 tags: vpc routing route-table private-network managed-route automatic-route local-subnet-route default-route
 dates:
-  validation: 2024-05-28
+  validation: 2024-12-03
   posted: 2024-05-28
 categories:
   - network