Skip to content

fix(docs): nw docs review #4122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 19, 2024
Merged

fix(docs): nw docs review #4122

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9bcf234
fix(docs): nw docs review
RoRoJ Dec 16, 2024
d3ddcac
Update network/load-balancer/reference-content/public-private-accessi…
RoRoJ Dec 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion faq/vpc.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ meta:
content:
h1: VPC
dates:
validation: 2024-05-28
validation: 2024-12-16
category: network
productIcon: VpcProductIcon
---
Expand Down
6 changes: 2 additions & 4 deletions network/load-balancer/how-to/create-manage-flex-ips.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ content:
paragraph: This page explains how to create and manage flexible IP addresses for your Scaleway Load Balancer
tags: load-balancer flexible-ip failover-ip flex-ip ip-address reverse reverse-dns
dates:
validation: 2024-06-10
validation: 2024-12-16
posted: 2023-12-05
categories:
- network
Expand Down Expand Up @@ -92,6 +92,4 @@ The steps below show how to delete a flexible IP that is not attached to a Load

4. Click **Delete flexible IP** to confirm.

The flexible IP is deleted.


The flexible IP is deleted.
11 changes: 5 additions & 6 deletions network/load-balancer/reference-content/public-private-accessibility.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,15 @@
---
meta:
title: Public vs private Load Balancers
description: Learn how to choose an appropriate accessibility setting for your Load Balancer
content:
description: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favouring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer.
h1: Public vs private Load Balancers
paragraph: Learn how to choose an appropriate accessibility setting for your Load Balancer
paragraph: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favouring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer.
tags: load-balancer public private accessibility
categories:
- load-balancer
- network
dates:
validation: 2024-06-14
validation: 2024-12-16
posted: 2024-06-14
---

Expand Down Expand Up @@ -48,10 +47,10 @@ A Load Balancer is defined as private when you choose the "private" accessibilit
- It does not allow the use of a Let's Encrypt [certificate](/network/load-balancer/concepts/#certificate) - only imported certificates are supported.
- It does not support multi-cloud IP addresses for its backend servers, since it is not directly connected to the internet. Routes to them are thus, not guaranteed.

A private Load Balancer can be used to balance requests between backends internally, where your backends' clients are in the same Private Network as the Load Balancer. The security of your infrastructure is strengthened, as the Load Balancer does not have a public IP address and is not accessible over the public internet.
A private Load Balancer can be used to balance requests between backends internally, where your backends' clients are in the same VPC as the Load Balancer. The security of your infrastructure is strengthened, as the Load Balancer does not have a public IP address and is not accessible over the public internet.

<Lightbox src="scaleway-private-lb.webp" alt="" />

When you attach a private Load Balancer to multiple Private Networks, it has an IP address in each one. The Load Balancer can then forward traffic to any resource or service attached to any of its Private Networks, thus allowing inter-Private-Networks load balancing. Scaleway's managed DNS also makes it possible to contact the Load Balancer over the Private Network without knowing its IP address (using `lb-name.pn-name`, which then resolves to its private IP address).
When you attach a private Load Balancer to multiple Private Networks, it has an IP address in each one. The Load Balancer can then forward traffic to any resource or service attached to any of its Private Networks, thus allowing inter-Private-Networks load balancing. Scaleway's managed DNS also makes it possible to contact the Load Balancer over the Private Network without knowing its IP address (using `lb-name.pn-name`, which then resolves to its private IP address). [VPC routing](/network/vpc/concepts/#routing) also allows Load Balancers on different Private Networks in the same VPC to communicate.

<Lightbox src="scaleway-privatelb-multipn.webp" alt="" />
Loading