more faq entries

thomas-tacquet · thomas-tacquet · commit 9644a54e5479 · 2024-12-27T16:56:29.000+01:00
diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx
@@ -186,4 +186,28 @@ solutions like Scaleway Object Storage.
 ## Why does my container have an instance running after deployment, even with min-scale 0?
 
 Currently, a new container instance will always start after each deployment, even if there is no traffic and the minimum
-scale is set to 0. This behavior is not configurable at this time.
+scale is set to 0. This behavior is not configurable at this time.
+
+## How can I store data in my Serverless ressource?
+
+Serverless ressources are by default [stateless](/serverless/containers/concepts/#stateless), local storage is ephemeral.
+
+In different use cases like saving results of analysis, exporting data etc... it can be important to save data. Serverless ressources can be connected to ressources from the Scaleway ecosystem.
+
+### Databases
+
+* **Serverless Databases**: Go full serverless and take the complexity out of PostgreSQL database operations.
+* **Managed MySQL / PostgreSQL**: Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* **Managed Database for Redis®**: Fully managed Redis®* in seconds.
+* **Managed MongoDB®**: Get the best of MongoDB® and Scaleway in one database.
+
+### Storage
+
+* **Object storage**: Multi-AZ resilient object storage service ensuring high availability for your data.
+* **Scaleway Glacier**: Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
+
+<Message type="tip">
+Explore all Scaleway products on the console and select the right product for your use case.
+
+Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versionning.
+</Message>
diff --git a/faq/serverless-functions.mdx b/faq/serverless-functions.mdx
@@ -219,3 +219,27 @@ solutions like Scaleway Object Storage.
 
 Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum
 scale is set to 0. This behavior is not configurable at this time.
+
+## How can I store data in my Serverless ressource?
+
+Serverless ressources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
+
+In different use cases like saving results of analysis, exporting data etc... it can be important to save data. Serverless ressources can be connected to ressources from the Scaleway ecosystem.
+
+### Databases
+
+* **Serverless Databases**: Go full serverless and take the complexity out of PostgreSQL database operations.
+* **Managed MySQL / PostgreSQL**: Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* **Managed Database for Redis®**: Fully managed Redis®* in seconds.
+* **Managed MongoDB®**: Get the best of MongoDB® and Scaleway in one database.
+
+### Storage
+
+* **Object storage**: Multi-AZ resilient object storage service ensuring high availability for your data.
+* **Scaleway Glacier**: Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
+
+<Message type="tip">
+Explore all Scaleway products on the console and select the right product for your use case.
+
+Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versionning.
+</Message>
diff --git a/faq/serverless-jobs.mdx b/faq/serverless-jobs.mdx
@@ -142,3 +142,27 @@ To add network restrictions on your resource, consult the [list of prefixes used
 ## Can I securely use sensitive information with Serverless Jobs?
 
 Yes, you can use sensitive data such as API secret keys, passwords, TLS/SSL certificates, or tokens. Serverless Jobs seamlessly integrates with [Secret Manager](/identity-and-access-management/secret-manager/), which allows you to securely reference sensitive information within your jobs. Refer to the [dedicated documentation](/serverless/jobs/how-to/reference-secret-in-job/) for more information.
+
+## How can I store data in my Serverless ressource?
+
+Serverless ressources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
+
+In different use cases like saving results of analysis, exporting data etc... it can be important to save data. Serverless ressources can be connected to ressources from the Scaleway ecosystem.
+
+### Databases
+
+* **Serverless Databases**: Go full serverless and take the complexity out of PostgreSQL database operations.
+* **Managed MySQL / PostgreSQL**: Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* **Managed Database for Redis®**: Fully managed Redis®* in seconds.
+* **Managed MongoDB®**: Get the best of MongoDB® and Scaleway in one database.
+
+### Storage
+
+* **Object storage**: Multi-AZ resilient object storage service ensuring high availability for your data.
+* **Scaleway Glacier**: Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
+
+<Message type="tip">
+Explore all Scaleway products on the console and select the right product for your use case.
+
+Some products are not listed but for example, on specific use cases Secret Manager can help you to store informations that requires versionning.
+</Message>
diff --git a/serverless/containers/concepts.mdx b/serverless/containers/concepts.mdx
@@ -134,6 +134,10 @@ The port parameter specifies the network port that your container listens on for
 
 The value defined in the port parameter will then be passed to your container during the deployment inside the `PORT` environment variable.
 
+<Message type="note">
+Only one HTTP port can be exposed per Serverless Container.
+</Message>
+
 ## Privacy policy
 
 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**).
diff --git a/serverless/containers/reference-content/containers-limitations.mdx b/serverless/containers/reference-content/containers-limitations.mdx
@@ -52,20 +52,22 @@ During the execution of the container, if the limits are exceeded, a restart occ
 
 In order to ensure the proper functioning of the product, we restrict the use of certain ports and environment variables
 
-* 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.
-* Unavailable custom ports
-  Do not make your containers listen on these ports which are used by our service.
-  * 8008
-  * 8012
-  * 8013
-  * 8022
-  * 9090
-  * 9091
-* Reserved environment variables:
-  * `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)
+### 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.
+
+### Unavailable custom ports
+Do not make your containers listen on these ports which are used by our service.
+* 8008
+* 8012
+* 8013
+* 8022
+* 9090
+* 9091
+
+### Reserved environment variables
+* `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)
 
 ## Default values for CPU and memory limits
 
diff --git a/serverless/functions/reference-content/functions-limitations.mdx b/serverless/functions/reference-content/functions-limitations.mdx
@@ -50,11 +50,13 @@ If the limits are exceeded during the execution of the function, a restart occur
 
 To ensure the proper functioning of the product, we restrict the use of certain ports and environment variables.
 
-* 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.
-* Reserved environment variables:
-  * `SCW_*`: Reserved for product configuration (for example: token validation).
+### 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.
+
+### Reserved environment variables:
+* `SCW_*`: Reserved for product configuration (for example: token validation).
 
 ## Versioning and rollback
 
