Skip to content

Int fix serverless routing #5361

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 3 commits into from
Aug 1, 2025
Merged

Int fix serverless routing #5361

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d3ba9a2
fix(vpc): serverless routing info
RoRoJ Jul 31, 2025
c97906c
fix(vpc): another precision
RoRoJ Jul 31, 2025
0cb3596
Apply suggestions from code review
RoRoJ Aug 1, 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: 5 additions & 1 deletion pages/vpc/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,11 @@ NACLs are currently in Public Beta, and configurable only via the [VPC API](http

### Why can I not route traffic to my Managed Database on another Private Network?

Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well.
Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well.

### Are Serverless Functions and Containers compatible with VPC routing?

No, Serverless Functions and Containers are not currently compatible with VPC routing. Functions and Containers attached to a Private Network support egress traffic only, towards other resources on the same Private Network.

### How are NACLs different from security groups?

Expand Down
1 change: 1 addition & 0 deletions pages/vpc/reference-content/understanding-routing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,4 +157,5 @@ Alternatively, and aligned with best practice, when the default NACL rule **Deni
## Limitations

- Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with VPC routing. Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well.
- Serverless Functions and Containers do not support VPC routing.
- VPC routing does not currently support virtual IPs.
5 changes: 3 additions & 2 deletions pages/vpc/troubleshooting/vpc-limitations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,12 +15,13 @@ This page sets out some current limitations of Scaleway's VPC.
- Instances
- Elastic Metal servers
- Apple silicon (Mac mini)
- Load Balancers
- Load Balancers.
- Public Gateways
- Managed Databases for PostgreSQL and MySQL
- Managed Databases for Redis™ (only during the process of creating the database)
- Kubernetes Kapsule (only during the process of creating the Kapsule cluster)
- Serverless Functions and Containers (egress traffic only, with VPC-supporting namespaces)
- Serverless Functions and Containers (egress traffic only, with VPC-supporting namespaces. Not compatible with VPC routing.)
- Private Networks are not supported on some legacy Instance offers which have reached EOL, e.g. `VC1`, `START1` and `X64-*GB`. Note that all Instance offers in the [current product catalogue](https://www.scaleway.com/en/pricing/?tags=compute) are supported.
- Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well.