Skip to content

fix(vpc): doc review #5798

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
Nov 14, 2025
Merged

fix(vpc): doc review #5798

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
110c9fe
fix(vpc): doc review
RoRoJ Nov 13, 2025
485ef77
fix(nats): concepts
RoRoJ Nov 13, 2025
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
6 changes: 3 additions & 3 deletions pages/public-gateways/how-to/configure-a-public-gateway.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: How to configure a Public Gateway
description: Learn how to configure a Public Gateway with the Scaleway console. Follow our step-by-step guide to set up routing, internet access, and SSH bastion for secure, scalable network connectivity.
tags: public-gateway public gateway dhcp nat smtp
dates:
validation: 2025-05-05
validation: 2025-11-13
posted: 2021-05-26
---
import Requirements from '@macros/iam/requirements.mdx'
Expand Down Expand Up @@ -46,7 +46,7 @@ Your Private Network is now attached to your Public Gateway. You can repeat the
Dynamic NAT is automatically activated. However, you can review and (if you wish) modify the NAT configuration of an existing Public Gateway as follows:

1. Click **Public Gateways** in the **Network** section of the side menu.
2. Click the Public Gateway whose configuration you wish to modify. You are taken to the Overview page for that Public Gateway.
2. Click the Public Gateway whose configuration you wish to modify. You are taken to the **Overview** page for that Public Gateway.
3. Click the **NAT** tab.
4. Use the toggle to deactivate dynamic NAT if desired. To add a new static NAT configuration for any Private Network attached to this gateway, click **Add Static NAT**. The following screen displays:
<Lightbox image={image} alt="" />
Expand All @@ -64,7 +64,7 @@ Dynamic NAT is automatically activated. However, you can review and (if you wish
By default, the SMTP ports (25, 465, 587 and 2525) on your Public Gateway are blocked to avoid spam. If you wish to send emails from resources located behind your Public Gateway, make sure those resources [have also enabled SMTP](/instances/how-to/send-emails-from-your-instance/) and then enable SMTP on your Public Gateway as follows:

1. Click **Public Gateways** in the **Network** section of the side menu.
2. Click the Public Gateway whose configuration you wish to modify. You are taken to the **Overview** page for that Public Gateway.
2. Click the Public Gateway whose configuration you wish to modify, then click the **Settings** tab.
3. Scroll down to the **SMTP** panel, and use the toggle <Icon name="toggle" /> to enable SMTP.

<Message type="important">
Expand Down
4 changes: 2 additions & 2 deletions pages/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: I cannot connect to my Instance using SSH after attaching it to a Private
description: This page explains how troubleshoot connection problems after attaching an Instance to a Private Network which has a Public Gateway
tags: troubleshoot error private-network private network vpc public-gateway
dates:
validation: 2025-05-05
validation: 2025-11-13
posted: 2021-05-26
---

Expand All @@ -27,7 +27,7 @@ If neither of the above scenarios applies, there may be other factors impacting

## Solution

If one of the above scenario applies, not being able to connect to your Instance via SSH is **expected behavior**. The Public Gateway's default route advertisement takes priority over the default route through a resource's public interface. All the traffic towards your Instance now goes through the Public Gateway.
If one of the above scenarios applies, not being able to connect to your Instance via SSH is **expected behavior**. The Public Gateway's default route advertisement takes priority over the default route through a resource's public interface. All the traffic towards your Instance now goes through the Public Gateway.

To access your Instance using SSH in this scenario, the recommended solution is to use [SSH bastion](/public-gateways/how-to/use-ssh-bastion/).

Expand Down
6 changes: 2 additions & 4 deletions pages/vpc/concepts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: VPC - Concepts
description: Discover the key concepts of Scaleway Virtual Private Cloud (VPC). Learn how to isolate, secure, and manage your cloud resources effectively.
tags: network vpc virtual-private-cloud regional private network routing
dates:
validation: 2025-05-05
validation: 2025-11-13
posted: 2023-02-06
---
import RegionAndAz from '@macros/console/region-and-az.mdx'
Expand Down Expand Up @@ -61,7 +61,7 @@ While DHCP is built into all new Private Networks, it may not be automatically a

The **D**omain **N**ame **S**ystem (DNS) is a naming system for devices connected to the internet or Private Networks. Most prominently, DNS servers translate text-based domain names (e.g. www.scaleway.com) to numerical IP addresses (e.g. `51.158.66.220`).

Private Networks benefit from managed DNS, which resolves the hostnames of attached resources into their IP addresses. The hostname for a given device is generally the name defined when creating the resource (and which in the case of an Instance, for example, displays in the shell when connected to that resource by SSH). See [full information](/vpc/reference-content/dns/) on Scaleway DNS and how to reach a resource via its hostname.
Scaleway Private Networks benefit from managed DNS, which resolves the hostnames of attached resources into their IP addresses. The hostname for a given device is generally the name defined when creating the resource (and which in the case of an Instance, for example, displays in the shell when connected to that resource by SSH). See [full information](/vpc/reference-content/dns/) on Scaleway DNS and how to reach a resource via its hostname.

## IPAM

Expand Down Expand Up @@ -102,8 +102,6 @@ Private Networks let you connect Scaleway resources across multiple AZs within t
Read our dedicated documentation on [creating a Private Network](/vpc/how-to/create-private-network/).

<Message type="note">
Previously, Private Networks at Scaleway were zoned. Only resources from within one defined AZ could be attached to each network. Now, all Private Networks are regional, and resources from any AZ within that network's region can be attached. "Old" zoned Private Networks have all been automatically migrated to become regional.

While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks. Check our [migration](/vpc/reference-content/vpc-migration/) documentation for more information.
</Message>

Expand Down
2 changes: 1 addition & 1 deletion pages/vpc/how-to/create-vpc.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: How to create and manage VPCs
description: Learn how to create a Virtual Private Cloud (VPC) with the Scaleway console. Follow this detailed guide to set up secure and isolated network infrastructure for your cloud resources.
tags: vpc default create regional virtual-private-cloud
dates:
validation: 2025-05-05
validation: 2025-11-13
posted: 2023-06-13
---
import Requirements from '@macros/iam/requirements.mdx'
Expand Down