From 7f36d8e6f0134719e695bb19940b383085d4dcbf Mon Sep 17 00:00:00 2001 From: Rowena Date: Mon, 14 Oct 2024 10:18:20 +0200 Subject: [PATCH] fix(nw): add links --- network/ipam/concepts.mdx | 2 +- network/ipam/index.mdx | 4 ++-- network/vpc/how-to/create-private-network.mdx | 2 +- network/vpc/index.mdx | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/network/ipam/concepts.mdx b/network/ipam/concepts.mdx index ea05c08a1e..53008919f8 100644 --- a/network/ipam/concepts.mdx +++ b/network/ipam/concepts.mdx @@ -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. +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/). 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. diff --git a/network/ipam/index.mdx b/network/ipam/index.mdx index fc17d6ecdd..13401fdd13 100644 --- a/network/ipam/index.mdx +++ b/network/ipam/index.mdx @@ -6,9 +6,9 @@ meta: - You can now reserve private IPs with IPAM, and use a reserved IP when attaching a specific resource to a Private Network. [Learn more about how to reserve an IP](/network/ipam/how-to/reserve-ip/). + Discover essential best practices for securing and optimizing public connectivity in your Scaleway cloud environment, with our [new guide](/network/ipam/reference-content/public-connectivity-best-practices/). Learn how to enhance performance and ensure robust protection. While DHCP is built into all new Private Networks, it may not be automatically activated for Private Networks created before July 2023. Check our [migration](/network/vpc/reference-content/vpc-migration/) documentation for more information. diff --git a/network/vpc/index.mdx b/network/vpc/index.mdx index 5f9c056109..a1795df18f 100644 --- a/network/vpc/index.mdx +++ b/network/vpc/index.mdx @@ -6,9 +6,9 @@ meta: - Try out the new [VPC routing](/network/vpc/concepts/#routing) feature, now in General Availability. Routing lets Private Networks in the same VPC communicate with each other, via automatically-created and managed routes. + Learn how to optimize your Scaleway VPCs, Private Networks and resource connectivity with [our new guide](/network/vpc/reference-content/getting-most-private-networks/) detailing tips and best practices.