diff --git a/network/load-balancer/how-to/create-load-balancer.mdx b/network/load-balancer/how-to/create-load-balancer.mdx index ec75136288..15b0be6114 100644 --- a/network/load-balancer/how-to/create-load-balancer.mdx +++ b/network/load-balancer/how-to/create-load-balancer.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to create a Load Balancer tags: load-balancer load balancer dates: - validation: 2024-03-26 + validation: 2024-10-04 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**). diff --git a/network/load-balancer/how-to/use-with-private-network.mdx b/network/load-balancer/how-to/use-with-private-network.mdx index 681f039d7f..d44da3b8fd 100644 --- a/network/load-balancer/how-to/use-with-private-network.mdx +++ b/network/load-balancer/how-to/use-with-private-network.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to use your Load Balancer with a Private Network tags: load-balancer private-network load balancer private network dates: - validation: 2024-03-26 + validation: 2024-10-04 posted: 2021-05-26 categories: - network diff --git a/network/load-balancer/reference-content/configuring-backends.mdx b/network/load-balancer/reference-content/configuring-backends.mdx index 8ece4043d7..ea5bfd099a 100644 --- a/network/load-balancer/reference-content/configuring-backends.mdx +++ b/network/load-balancer/reference-content/configuring-backends.mdx @@ -10,7 +10,7 @@ categories: - load-balancer - network dates: - validation: 2024-03-26 + validation: 2024-10-04 posted: 2023-06-05 --- diff --git a/network/vpc/assets/scaleway-attach-resource.webp b/network/vpc/assets/scaleway-attach-resource.webp index 9a72c35895..014950e561 100644 Binary files a/network/vpc/assets/scaleway-attach-resource.webp and b/network/vpc/assets/scaleway-attach-resource.webp differ diff --git a/network/vpc/assets/scaleway-create-pn.webp b/network/vpc/assets/scaleway-create-pn.webp index ec5a13d815..121ce89a43 100644 Binary files a/network/vpc/assets/scaleway-create-pn.webp and b/network/vpc/assets/scaleway-create-pn.webp differ diff --git a/network/vpc/assets/scaleway-route-table.webp b/network/vpc/assets/scaleway-route-table.webp new file mode 100644 index 0000000000..df9ab11745 Binary files /dev/null and b/network/vpc/assets/scaleway-route-table.webp differ diff --git a/network/vpc/quickstart.mdx b/network/vpc/quickstart.mdx index 31b7e2a641..9b9b8cb250 100644 --- a/network/vpc/quickstart.mdx +++ b/network/vpc/quickstart.mdx @@ -7,7 +7,7 @@ content: paragraph: This page shows you how to get started with Scaleway Virtual Private Cloud (VPC). tags: vpc virtual-private-cloud regional private network dhcp private-ip dates: - validation: 2024-03-26 + validation: 2024-10-04 posted: 2022-02-06 categories: - network @@ -39,16 +39,12 @@ Any new Private Networks that you create will be added to the default VPC for th 1. Click **VPC** in the **Network** section of the side menu. The list of your VPCs displays: - - Each Private Network must be created within a VPC. 2. Click the VPC you wish to create your Private Network in. If you already have existing Private Networks in this VPC, a list of these displays. Otherwise, you see a welcome screen. - - 3. Click **+ Create Private Network**. The creation screen displays. @@ -57,7 +53,7 @@ Any new Private Networks that you create will be added to the default VPC for th - Leave the Advanced Settings at default values, to create a network with an auto-generated CIDR block, which will be used by DHCP to assign private IP addresses to resources you attach to the network. + Leave the Advanced Settings at default values, to create a network with an auto-generated CIDR block. IP addresses for attached resources will come from this block. 5. Click **Create Private Network** to finish. Your Private Network is created. @@ -65,8 +61,6 @@ Any new Private Networks that you create will be added to the default VPC for th 1. Click **VPC** in the **Network** section of the side menu. Your VPC [dashboard](https://console.scaleway.com/vpc/vpc) displays: - - 2. Click the VPC containing the Private Network to which you want to attach a resource. A list of Private Networks in this VPC displays. @@ -75,8 +69,6 @@ Any new Private Networks that you create will be added to the default VPC for th The Private Network's dashboard displays. - - 4. Click the **Attached resources** tab. If you already have resources attached to the Private Network, a list of these displays. Otherwise, you see a welcome screen. @@ -93,19 +85,35 @@ Any new Private Networks that you create will be added to the default VPC for th Support for using reserved IPs to attach Elastic Metal servers and Managed Databases to Private Networks will be coming soon. -7. Click **Attach resource** to finish. +7. Click **Attach to Private Network** to finish. You are returned to the list of attached resources, where the newly-attached resource now displays. -## How to view the resource's IP address + + **Viewing the resource's private IP**: When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). Private IPs are assigned from the CIDR block defined at the time of the Private Network's creation, either via auto-assignment or specification of a particular [reserved IP](/network/ipam/how-to/reserve-ip/). You can view a resource's IPv4 or v6 address in the **Attached Resources** tab of the Private Network itself (follow steps 1 - 4 above). It can also be viewed via the **Private Networks** tab of the resource's own dashboard. + + +## How to manage routing + +Routing is used to manage and control the flow of traffic within a VPC. It tells the VPC where to send traffic trying to get to a specific destination IP address. Notably, it allows traffic to be automatically routed between resources attached to different Private Networks within the VPC, using their private IP addresses. You can also create your own custom routes. + +Your VPC’s route table can be found in its **Routing** tab. The route table shows all the existing routes for the VPC. + +1. Click VPC in the **Network** section of the side menu. The list of your VPCs displays. + +2. Click a VPC, and click the **Routing** tab. + + Routes are automatically generated and added to the route table when you: -When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). Private IPs are assigned from the CIDR block defined at the time of the Private Network's creation, either via auto-assignment or specification of a particular [reserved IP](/network/ipam/how-to/reserve-ip/). + - [Create a Private Network](#how-to-create-a-private-network) in the VPC (this generates a local subnet route, which allows the VPC to automatically route traffic between Private Networks), or + - [Attach a Public Gateway](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) to a Private Network and set it to advertise a default route. This generates a default route to the internet. + - [Create a custom route](/network/vpc/how-to/manage-routing/#how-to-create-a-custom-route). -You can view a resource's IPv4 or v6 address in the **Attached Resources** tab of the Private Network itself (follow steps 1 - 4 above). +When your route table starts to populate, it will look something like this: - + -It can also be viewed via the **Private Networks** tab of the resource's own dashboard. +For help with understanding the route table and how to read it, refer to our documentation about route tables. ## How to delete a Private Network