Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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 network/ipam/concepts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
4 changes: 2 additions & 2 deletions network/ipam/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ meta:

<Alert
sentiment="info"
title="Reserve IPs with IPAM"
title="Public connectivity - best practices"
>
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.
</Alert>

<ProductHeader
Expand Down
2 changes: 1 addition & 1 deletion network/vpc/how-to/create-private-network.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ categories:

VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. Within each VPC, you can create multiple **Private Networks** and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region. Attached resources can then communicate between themselves in an isolated and secure layer 2 network, away from the public internet.

Private Networks also have built-in **D**ynamic **H**ost **C**onfiguration **P**rotocol (DHCP), making it easy to manage the private IP addresses of your resources on the network. IPs are statically allocated when resources are attached to a Private Network, and are managed by our internal [IPAM](/network/vpc/concepts/#ipam).
Private Networks also have built-in **D**ynamic **H**ost **C**onfiguration **P**rotocol (DHCP), making it easy to manage the private IP addresses of your resources on the network. IPs are statically allocated when resources are attached to a Private Network, and are managed by our internal [IPAM](/network/vpc/concepts/#ipam). You can find out how to get the most from your Private Networks in our [dedicated guide](/network/vpc/reference-content/getting-most-private-networks/).

<Message type="note">
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.
Expand Down
4 changes: 2 additions & 2 deletions network/vpc/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@ meta:

<Alert
sentiment="info"
title="VPC routing is now in General Availability"
title="Getting the most from your Private Networks"
>
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.
</Alert>

<ProductHeader
Expand Down