scaleway · SamyOubouaziz · Feb 6, 2025 · Feb 5, 2025 · Feb 5, 2025 · Feb 5, 2025
diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx
@@ -187,7 +187,7 @@ Protocol switching is available in the Console under the `Advanced options` sect
 
 Containers use **http1** by default, yet the gRPC protocol requires `http2`. You can upgrade the protocol to `http2` (`h2c`).
 
-### How can I configure access to a Private Network?
+### How can I configure access to a Private Network or Virtual Private Cloud (VPC)?
 
 Scaleway Serverless Containers does not currently support Scaleway VPC or Private Networks, though this feature is under development.
 

diff --git a/faq/serverless-functions.mdx b/faq/serverless-functions.mdx
@@ -214,7 +214,7 @@ Upgrading a runtime is highly recommended in case of deprecation, and for runtim
 
 ## Network and storage
 
-### How do I configure access to a Private Network?
+### How can I configure access to a Private Network or Virtual Private Cloud (VPC)?
 
 Scaleway Serverless Functions does not currently support Scaleway VPC or Private Networks, though this feature is under development.
 

diff --git a/faq/serverless-jobs.mdx b/faq/serverless-jobs.mdx
@@ -147,7 +147,7 @@ Yes, you can use sensitive data such as API secret keys, passwords, TLS/SSL cert
 
 ## Network and storage
 
-### How can I configure access to a Private Network?
+### How can I configure access to a Private Network or Virtual Private Cloud (VPC)?
 
 Scaleway Serverless Jobs does not currently support Scaleway VPC or Private Networks, though this feature is under development.
 

diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx
@@ -152,6 +152,10 @@ Only one HTTP port can be exposed per Serverless Container.
 
 A container's privacy policy defines whether a container may be invoked anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**).
 
+## Private Networks compatibility
+
+Refer to the [dedicated FAQ](/faq/serverless-containers/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Containers compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).
+
 ## Queue trigger
 
 A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/messaging/concepts/#queues), and invokes the container automatically whenever a message is added to the queue.

diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx
@@ -73,6 +73,10 @@ Do not have your containers listen on these ports, as they are used by our servi
 * `PORT`: Value of the port defined in the Container settings, which the container has to listen on. You can use this environment variable inside your Container for easier deployments.
 * `SCW_*`: Reserved for product configuration (for example: token validation)
 
+## Private Network and Virtual Private Cloud (VPC) compatibility
+
+Refer to the [dedicated FAQ](/faq/serverless-containers/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Containers compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).
+
 ## Default values for CPU and memory limits
 
 When container CPU and/or memory are not provided by the client, these default values are automatically used:

diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx
@@ -112,6 +112,10 @@ The function can then process the message and perform any required actions, such
 
 A function's privacy policy defines whether a function may be executed anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-functions/#authentication) (**private**).
 
+## Private Networks compatibility
+
+Refer to the [dedicated FAQ](/faq/serverless-functions/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Functions compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).
+
 ## Queue trigger
 
 A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/messaging/concepts/#queues), and invokes the function automatically whenever a message is added to the queue.

diff --git a/pages/serverless-functions/reference-content/functions-limitations.mdx b/pages/serverless-functions/reference-content/functions-limitations.mdx
@@ -61,6 +61,10 @@ Due to potential abuse (spam), no outbound traffic is allowed through following
 ### Reserved environment variables:
 * `SCW_*`: Reserved for product configuration (for example: token validation).
 
+## Private Network and Virtual Private Cloud (VPC) compatibility
+
+Refer to the [dedicated FAQ](/faq/serverless-functions/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Functions compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).
+
 ## Versioning and rollback
 
 Scaleway Functions do not currently support versioning or automatic rollback mechanisms.

diff --git a/pages/serverless-jobs/concepts.mdx b/pages/serverless-jobs/concepts.mdx
@@ -56,6 +56,10 @@ The maximum duration option allows you to define the maximum execution time befo
 
 Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Jobs](/serverless-jobs/how-to/monitor-job/).
 
+## Private Networks compatibility
+
+Refer to the [dedicated FAQ](/faq/serverless-jobs/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Jobs compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).
+
 ## Schedule (cron)
 
 A schedule (cron) is a mechanism used to automatically start a Serverless Job at a specific time on a recurring schedule. It works similarly to a traditional Linux cron job, using the `* * * * *` format. Refer to our [cron schedules reference](/serverless-jobs/reference-content/cron-schedules/) for more information.

diff --git a/pages/serverless-jobs/reference-content/jobs-limitations.mdx b/pages/serverless-jobs/reference-content/jobs-limitations.mdx
@@ -54,3 +54,7 @@ In order to ensure the proper functioning of the product, we restrict the use of
 * Blocked ports:
   * **25**: Due to potential abuse (spam), no outbound traffic is allowed through this port, except from Scaleway Transactional Email SMTP servers.
   * **465**: Due to potential abuse (spam), no outbound traffic is allowed through this port, except from Scaleway Transactional Email SMTP servers.
+
+## Private Network and Virtual Private Cloud (VPC) compatibility
+
+Refer to the [dedicated FAQ](/faq/serverless-jobs/#how-can-i-configure-access-to-a-private-network-or-virtual-private-cloud-vpc) for more information on Serverless Jobs compatibility with Private Networks and [Virtual Private Cloud (VPC)](/vpc/).