Skip to content

Commit 0fd7171

Browse files
authored
fix(network): doc review (#4073)
1 parent bffedc6 commit 0fd7171

File tree

6 files changed

+35
-34
lines changed

6 files changed

+35
-34
lines changed

network/ipam/concepts.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
meta:
33
title: IPAM - Concepts
4-
description: This page explains all the concepts related to IPAM
4+
description: Learn about IP Address Management (IPAM) concepts with Scaleway. Understand how to organize, allocate, and manage IP resources efficiently in your cloud infrastructure.
55
content:
66
h1: IPAM - Concepts
7-
paragraph: This page explains all the concepts related to IPAM
7+
paragraph: Learn about IP Address Management (IPAM) concepts with Scaleway. Understand how to organize, allocate, and manage IP resources efficiently in your cloud infrastructure.
88
tags: ipam ip-address-management internet-protocol private-ip public-ip flexible-ip list-ips book-ip
99
dates:
10-
validation: 2024-05-30
10+
validation: 2024-12-03
1111
categories:
1212
- networks
1313
---
@@ -37,7 +37,7 @@ Scaleway resources may have a [public](#public-flexible-ip-address) IPv4 address
3737

3838
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`.
3939

40-
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.
40+
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/).
4141

4242
## Private IP address
4343

@@ -51,7 +51,7 @@ Four IP addresses from each CIDR block are unavailable for reservation/use: the
5151

5252
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.
5353

54-
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/).
54+
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/).
5555

5656
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.
5757

network/load-balancer/how-to/manage-frontends-and-backends.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
meta:
33
title: How to manage frontends and backends
4-
description: This page explains how to add frontends and backends
4+
description: Learn how to manage frontends and backends with Scaleway Load Balancer. Configure endpoints, optimize traffic flow, and ensure seamless application performance.
55
content:
66
h1: How to manage frontends and backends
7-
paragraph: This page explains how to add frontends and backends
7+
paragraph: Learn how to manage frontends and backends with Scaleway Load Balancer. Configure endpoints, optimize traffic flow, and ensure seamless application performance.
88
tags: load-balancer frontend backend
99
dates:
10-
validation: 2024-05-27
10+
validation: 2024-12-03
1111
posted: 2021-05-26
1212
categories:
1313
- network

network/load-balancer/quickstart.mdx

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
meta:
33
title: Load Balancers - Quickstart
4-
description: This page shows you how to get started with Scaleway Load Balancers.
4+
description: Get started with Scaleway Load Balancer in minutes. Follow this quickstart guide to set up, configure, and optimize traffic distribution for your applications.
55
content:
66
h1: Load Balancers - Quickstart
7-
paragraph: This page shows you how to get started with Scaleway Load Balancers.
7+
paragraph: TGet started with Scaleway Load Balancer in minutes. Follow this quickstart guide to set up, configure, and optimize traffic distribution for your applications.
88
tags: load-balancer load balancer frontend backend
99
dates:
10-
validation: 2024-05-27
10+
validation: 2024-12-03
1111
posted: 2021-05-26
1212
categories:
1313
- network
@@ -28,15 +28,7 @@ categories:
2828

2929
3. Enter a **name** for your Load Balancer. Optionally, you can also add a **description** and assign **tags** to help organize your Load Balancers.
3030

31-
4. Choose the **Availability Zone** in which your Load Balancer will be deployed geographically. Currently, we provide the following Availability Zones:
32-
- `PAR1`: Paris 1, France.
33-
- `PAR2`: Paris 2, France (innovative and sustainable Availability Zone).
34-
- `AMS1`: Amsterdam, The Netherlands.
35-
- `AMS2`: Amsterdam 2, The Netherlands.
36-
- `AMS3`: Amsterdam 3, The Netherlands.
37-
- `WAW1`: Warsaw, Poland.
38-
- `WAW2`: Warsaw, Poland.
39-
- `WAW3`: Warsaw, Poland.
31+
4. Choose the **Availability Zone** in which your Load Balancer will be deployed geographically.
4032

4133
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**).
4234

@@ -92,6 +84,15 @@ Continue to the next section for configuring health checks.
9284

9385
When you have finished configuring your frontend and backend, click **Create frontend and backend** at the bottom of the page to finish.
9486

87+
## How to finish configuring your Load Balancer
88+
89+
Depending on your use case, you may need to carry out further configuration on your Load Balancer. Refer to the following documentation:
90+
91+
- [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/)
92+
- [Attach a Load Balancer to a Private Network](/network/load-balancer/how-to/use-with-private-network/)
93+
- Set up Load Balancer [ACLs](/network/load-balancer/how-to/create-manage-acls/) or [routes](/network/load-balancer/how-to/create-manage-routes/)
94+
- [Create an Edge Services pipeline](/network/load-balancer/how-to/use-edge-services/) for your Load Balancer
95+
9596
## How to delete a Load Balancer
9697

9798
1. Click **Load Balancers** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Load Balancer dashboard displays.

network/vpc/concepts.mdx

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
meta:
33
title: VPC - Concepts
4-
description: This page explains all the concepts related to VPC
4+
description: Discover the key concepts of Scaleway Virtual Private Cloud (VPC). Learn how to isolate, secure, and manage your cloud resources effectively.
55
content:
66
h1: VPC - Concepts
7-
paragraph: This page explains all the concepts related to VPC
8-
tags: network vpc virtual-private-cloud regional private network
7+
paragraph: Discover the key concepts of Scaleway Virtual Private Cloud (VPC). Learn how to isolate, secure, and manage your cloud resources effectively.
8+
tags: network vpc virtual-private-cloud regional private network routing
99
categories:
1010
- network
1111
dates:
12-
validation: 2024-05-30
12+
validation: 2024-12-03
1313
posted: 2023-02-06
1414
---
1515

@@ -30,9 +30,9 @@ Scaleway currently has three regions: Paris, Amsterdam and Warsaw. One default V
3030

3131
**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.
3232

33-
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.
33+
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.
3434

35-
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.
35+
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.
3636

3737
The IPv4 address of Private Networks' DHCP server is `169.254.169.254`. The IPv6 address is `fe80:200:22ff:fe05:ca1e`.
3838

@@ -56,13 +56,13 @@ Private Networks benefit from managed DNS, which resolves the hostnames of attac
5656

5757
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`.
5858

59-
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.
59+
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/).
6060

6161
## IPv6
6262

6363
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`.
6464

65-
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.
65+
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/).
6666

6767
## Private IP address
6868

network/vpc/how-to/manage-routing.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
meta:
33
title: How to manage routing
4-
description: This page explains how to manage routing in your Scaleway VPC
4+
description: Learn how to manage routing in Scaleway Virtual Private Cloud (VPC). Configure custom routes to control traffic flow and optimize network performance.
55
content:
66
h1: How to manage routing
7-
paragraph: This page explains how to manage routing in your Scaleway VPC
7+
paragraph: Learn how to manage routing in Scaleway Virtual Private Cloud (VPC). Configure custom routes to control traffic flow and optimize network performance.
88
tags: private-network vpc routing route-table routes default-route local-route subnet
99
dates:
10-
validation: 2024-05-28
10+
validation: 2024-12-03
1111
posted: 2024-04-09
1212
categories:
1313
- network

network/vpc/reference-content/understanding-routing.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
meta:
33
title: Understanding VPC routing
4-
description: This page provides detailed information about the VPC routing feature, which connects Private Networks within the same VPC.
4+
description: Explore the fundamentals of VPC routing with Scaleway. Understand how to manage traffic flow and optimize network routes within your Virtual Private Cloud
55
content:
66
h1: Understanding VPC routing
7-
paragraph: This page provides detailed information about the VPC routing feature, which connects Private Networks within the same VPC.
7+
paragraph: Explore the fundamentals of VPC routing with Scaleway. Understand how to manage traffic flow and optimize network routes within your Virtual Private Cloud
88
tags: vpc routing route-table private-network managed-route automatic-route local-subnet-route default-route
99
dates:
10-
validation: 2024-05-28
10+
validation: 2024-12-03
1111
posted: 2024-05-28
1212
categories:
1313
- network

0 commit comments

Comments
 (0)