From b383f8da802e1f421b383fac71a6342c5f0e1add Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Thu, 7 May 2026 12:26:34 +0200 Subject: [PATCH 1/3] docs(load-balancers): update creation form --- .../how-to/create-load-balancer.mdx | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/pages/load-balancer/how-to/create-load-balancer.mdx b/pages/load-balancer/how-to/create-load-balancer.mdx index 56acab4ea1..1ad5ad9834 100644 --- a/pages/load-balancer/how-to/create-load-balancer.mdx +++ b/pages/load-balancer/how-to/create-load-balancer.mdx @@ -22,22 +22,22 @@ import Requirements from '@macros/iam/requirements.mdx' 2. Click **Create Load Balancer** or the button. The creation wizard displays. -3. Enter a **name** for your Load Balancer. Optionally, you can also add a **description** and assign **tags** to help organize your Load Balancers. +3. Choose the **Availability Zone** in which your Load Balancer will be deployed geographically. -4. Choose the **Availability Zone** in which your Load Balancer will be deployed geographically. +4. 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**). -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**). +5. Set up public connectivity to access your Load Balancer from the internet. + - A public [IPv4](/load-balancer/concepts/#ipv4) address is obligatory. You can either allocate a new IPv4 address, or select one of your [existing flexible IPv4 addresses](/load-balancer/how-to/create-manage-flex-ips/). + - You can optionally add a public [IPv6](/load-balancer/concepts/#ipv6) address in addition to the IPv4 address. You can either allocate a new IPv6 address, or select one of your [existing flexible IPv6 addresses](/load-balancer/how-to/create-manage-flex-ips/). -6. Select the **accessibility** of your Load Balancer. Choose either: - - **Private**: A private Load Balancer will have no public IP address, and is only accessible from the Private Network(s) it is attached to. You can [attach your Load Balancer to a Private Network](/load-balancer/how-to/use-with-private-network/) after creation of the Load Balancer. [Read more about private Load Balancers](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). - - **Public**: A public Load Balancer is accessible from the internet via its public IP address. You must choose from the following IP options: - - **IPv4**: A public [IPv4](/load-balancer/concepts/#ipv4) address is obligatory. You can either allocate a new IPv4 address, or select one of your [existing flexible IPv4 addresses](/load-balancer/how-to/create-manage-flex-ips/). - - **IPv6**: You can optionally add a public [IPv6](/load-balancer/concepts/#ipv6) address in addition to the IPv4 address. You can either allocate a new IPv6 address, or select one of your [existing flexible IPv6 addresses](/load-balancer/how-to/create-manage-flex-ips/). + Accessibility cannot be modified after creation of the Load Balancer. - Accessibility cannot be modified after creation of the Load Balancer. For more information about managing your Load Balancer's public IPs, see our [dedicated documentation](/load-balancer/how-to/create-manage-flex-ips/). + + You can set up private connectivity by [attaching a Private Network](/load-balancer/how-to/use-with-private-network/) to your Load Balancer after its creation. + -7. Choose one of the following options: - - Click **Create Load Balancer** to finish now and create your Load Balancer without any frontends or backends. You can configure and add frontends and backends to your Load Balancer whenever you want after creation. - - Click **Create and add front and backend** to create your Load Balancer and also immediately proceed to configuring a frontend and backend for it. See [how to create frontends and backends](/load-balancer/how-to/create-frontends-backends/) for help with this step. +6. Enter a **name** for your Load Balancer. Optionally, you can also add a **description** and assign **tags** to help organize your Load Balancers. +7. Click **Create Load Balancer** to finish. A confirmation pop-up displays. +8. Click **Configure now** to set up a frontend, a backend, traffic management, and health checks for your Load Balancer, or do it at a later time. From 79fea48377ceedb8fc824c8f705daab583af0c51 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Thu, 7 May 2026 13:42:22 +0200 Subject: [PATCH 2/3] docs(load-balancers): update --- .../how-to/create-load-balancer.mdx | 4 +--- pages/load-balancer/quickstart.mdx | 24 +++++++++---------- 2 files changed, 13 insertions(+), 15 deletions(-) diff --git a/pages/load-balancer/how-to/create-load-balancer.mdx b/pages/load-balancer/how-to/create-load-balancer.mdx index 1ad5ad9834..f7b95a7c11 100644 --- a/pages/load-balancer/how-to/create-load-balancer.mdx +++ b/pages/load-balancer/how-to/create-load-balancer.mdx @@ -30,10 +30,8 @@ import Requirements from '@macros/iam/requirements.mdx' - A public [IPv4](/load-balancer/concepts/#ipv4) address is obligatory. You can either allocate a new IPv4 address, or select one of your [existing flexible IPv4 addresses](/load-balancer/how-to/create-manage-flex-ips/). - You can optionally add a public [IPv6](/load-balancer/concepts/#ipv6) address in addition to the IPv4 address. You can either allocate a new IPv6 address, or select one of your [existing flexible IPv6 addresses](/load-balancer/how-to/create-manage-flex-ips/). - Accessibility cannot be modified after creation of the Load Balancer. - - You can set up private connectivity by [attaching a Private Network](/load-balancer/how-to/use-with-private-network/) to your Load Balancer after its creation. + If you require public connectivity, you must enable it during Load Balancer creation as it cannot be added afterward. You can set up private connectivity by [attaching a Private Network](/load-balancer/how-to/use-with-private-network/) to your Load Balancer after its creation. 6. Enter a **name** for your Load Balancer. Optionally, you can also add a **description** and assign **tags** to help organize your Load Balancers. diff --git a/pages/load-balancer/quickstart.mdx b/pages/load-balancer/quickstart.mdx index 8e47b598f4..cb3896c099 100644 --- a/pages/load-balancer/quickstart.mdx +++ b/pages/load-balancer/quickstart.mdx @@ -28,25 +28,25 @@ import image from './assets/scaleway-configure-frontend.webp' 2. Click **+ Create Load Balancer**. The creation wizard displays. -3. Enter a **name** for your Load Balancer. Optionally, you can also add a **description** and assign **tags** to help organize your Load Balancers. +3. Choose the **Availability Zone** in which your Load Balancer will be deployed geographically. -4. Choose the **Availability Zone** in which your Load Balancer will be deployed geographically. +4. 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**). -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**). +5. Set up public connectivity to access your Load Balancer from the internet. + - A public [IPv4](/load-balancer/concepts/#ipv4) address is obligatory. You can either allocate a new IPv4 address, or select one of your [existing flexible IPv4 addresses](/load-balancer/how-to/create-manage-flex-ips/). + - You can optionally add a public [IPv6](/load-balancer/concepts/#ipv6) address in addition to the IPv4 address. You can either allocate a new IPv6 address, or select one of your [existing flexible IPv6 addresses](/load-balancer/how-to/create-manage-flex-ips/). -6. Select the **accessibility** of your Load Balancer. Choose either: - - **Private**: A private Load Balancer will have no public IP address, and is only accessible from the Private Network(s) it is attached to. You can [attach your Load Balancer to a Private Network](/load-balancer/how-to/use-with-private-network/) after creation of the Load Balancer. [Read more about private Load Balancers](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). - - **Public**: A public Load Balancer is accessible from the internet via its public IP address. You must choose from the following IP options: - - **IPv4**: A public [IPv4](/load-balancer/concepts/#ipv4) address is obligatory. You can either allocate a new IPv4 address, or select one of your [existing flexible IPv4 addresses](/load-balancer/how-to/create-manage-flex-ips/). - - **IPv6**: You can optionally add a public [IPv6](/load-balancer/concepts/#ipv6) address in addition to the IPv4 address. You can either allocate a new IPv6 address, or select one of your [existing flexible IPv6 addresses](/load-balancer/how-to/create-manage-flex-ips/). + + If you require public connectivity, you must enable it during Load Balancer creation as it cannot be added afterward. You can set up private connectivity by [attaching a Private Network](/load-balancer/how-to/use-with-private-network/) to your Load Balancer after its creation. + - Accessibility cannot be modified after creation of the Load Balancer. +6. Enter a **name** for your Load Balancer. Optionally, you can also add a **description** and assign **tags** to help organize your Load Balancers. -7. Click **Create and add front and backend** to create your Load Balancer, and configure a frontend and backend for it. +7. Click **Create Load Balancer** to finish. A confirmation pop-up displays. -## How to configure your frontend +8. Click **Configure now** to set up a frontend, a backend, traffic management, and health checks for your Load Balancer, or do it at a later time. - +## How to configure your frontend 1. Enter a **name** for your frontend. From bfd73189ee9b23e40e3ffda55917094e7189ec6c Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Thu, 7 May 2026 13:48:01 +0200 Subject: [PATCH 3/3] docs(load-balancers): update --- pages/load-balancer/quickstart.mdx | 3 --- 1 file changed, 3 deletions(-) diff --git a/pages/load-balancer/quickstart.mdx b/pages/load-balancer/quickstart.mdx index cb3896c099..101cf384e4 100644 --- a/pages/load-balancer/quickstart.mdx +++ b/pages/load-balancer/quickstart.mdx @@ -12,9 +12,6 @@ import LbCreateBackend2TrafficMgnt from '@macros/network/lb-create-backend-2-tra import LbCreateBackend3AdvancedSettings from '@macros/network/lb-create-backend-3-advanced-settings.mdx' import LbCreateBackend4Healthcheck from '@macros/network/lb-create-backend-4-healthcheck.mdx' -import image from './assets/scaleway-configure-frontend.webp' - - [Load Balancers](https://www.scaleway.com/en/load-balancer/) are highly available and fully-managed Instances which allow you to distribute your workload across your various servers. They ensure the scaling of all your applications while securing their continuous availability, even in the event of heavy traffic. Load Balancers are commonly used to improve the performance and reliability of websites, applications, databases and other services.