scaleway · SamyOubouaziz · Jan 14, 2025 · Jan 14, 2025 · Jan 14, 2025 · Jan 14, 2025
@@ -7,14 +7,13 @@ content:
   paragraph: Enable and enforce Multi-Factor Authentication (MFA).
 tags: authentication 2FA two-factor two multi factor security google authenticator authenticator mfa
 dates:
-  validation: 2024-07-02
+  validation: 2025-01-15
   posted: 2023-06-12
 categories:
   - console
 ---
 
-Multifactor Authentication (MFA) adds an extra layer of security to your Organization. Enforcing MFA will make it mandatory
-for all users in the Organization.
+[Multifactor Authentication (MFA)](/console/account/concepts/#multifactor-authentication-mfa) adds an extra layer of security to your Organization. Enforcing MFA will make it mandatory for all users in the Organization.
 
 <Macro id="requirements" />
 
@@ -29,13 +28,13 @@ for all users in the Organization.
 4. Click **Enforce MFA**.
 5. Type **ENFORCE** in the box.
     <Message type="important">
-      Be aware that MFA will become mandatory for all users in the Organization. When you invite users to your Organization in the future, they must have set up MFA to be able to join. <br /><br />
-      You can only enforce MFA if all users in your Organization have already set up MFA on their accounts.
+    MFA will become mandatory for all users in the Organization. When you invite users to your Organization in the future, they must have set up MFA to be able to join. <br /><br />
+    You can only enforce MFA if all users in your Organization have already set up MFA on their accounts.
     </Message>
 6. Click **Enforce MFA**.
-    If 100% of users in your Organization already have MFA enabled, a confirmation message appears on the top right corner of the screen.
+    - If all users in your Organization already have MFA enabled, a confirmation message appears on the top right corner of the screen.
 
-    If, however, at least one of the users does not have MFA enabled, you must send them an [MFA reminder](#how-to-send-an-mfa-reminder).
+    - If at least one of the users does not have MFA enabled, you must send them an [MFA reminder](#how-to-send-an-mfa-reminder).
 
     <Message type="important">
       If you invite users who are not yet a part of your Organization, they must enable MFA before joining.
@@ -46,7 +45,7 @@ for all users in the Organization.
 1. Click **IAM** in the top right drop-down menu. The IAM dashboard displays.
 2. Go to the **Users** tab.
 3. Click <Icon name="more" /> > **Send MFA reminder** next to the name of a user that has MFA disabled.
-    An email is sent to the user requesting that they enable MFA.
+    The user will receive an email requesting that they enable MFA.
 
 ## How to stop enforcing MFA
 

@@ -7,7 +7,7 @@ content:
   paragraph: Enable and use Two-Factor Authentication (2FA) in Scaleway.
 tags: authentication 2FA two-factor two multi factor security google authenticator authenticator
 dates:
-  validation: 2024-07-02
+  validation: 2025-01-15
   posted: 2022-01-14
 categories:
   - console
@@ -23,7 +23,7 @@ Multifactor authentication provides extra layers of security. In addition to you
 
 ## How to download an MFA app
 
-To use multifactor authentication on your account, you first need to download an MFA app onto your smartphone. Once configured, MFA apps display a constantly rotating set of codes to use with your different accounts when you are prompted for one during login. Popular MFA apps include:
+To use [multifactor authentication](/console/account/concepts/#multifactor-authentication-mfa) on your account, you first need to download an MFA app onto your smartphone. Once configured, MFA apps display a constantly rotating set of codes to use with your different accounts when you are prompted for one during login. Popular MFA apps include:
 - [Authy](https://authy.com/download/)
 - [FreeOTP](https://freeotp.github.io/)
 - [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=en&gl=US)

diff --git a/macros/serverless/cron-schedules.mdx b/macros/serverless/cron-schedules.mdx
@@ -9,15 +9,15 @@ Adding a cron schedule to a specific task allows you to run it automatically at
 Cron jobs are expressed using the `* * * * *` format, which corresponds to the fields below.
 
 ```
-# ┌───────────── minute
-# │ ┌───────────── hour 
-# │ │ ┌───────────── day of the month 
-# │ │ │ ┌───────────── month 
-# │ │ │ │ ┌───────────── day of the week
-# │ │ │ │ │ 
-# │ │ │ │ │
-# │ │ │ │ │
-# * * * * *
+  ┌───────────── minute
+  │ ┌───────────── hour 
+  │ │ ┌───────────── day of the month 
+  │ │ │ ┌───────────── month 
+  │ │ │ │ ┌───────────── day of the week
+  │ │ │ │ │ 
+  │ │ │ │ │
+  │ │ │ │ │
+  * * * * *
 ```
 
 Each field supports a specific range of values.

diff --git a/macros/serverless/difference-jobs-functions-containers.mdx b/macros/serverless/difference-jobs-functions-containers.mdx
@@ -18,16 +18,16 @@ macro: difference-jobs-functions-containers
 | **Scaling**                        | Automatically scales based on incoming events                       | Automatically scales based on incoming events                       | Manually specified number of job executions             |
 | **Maximum execution time**         | Up to 15 minutes per request                                        | Up to 15 minutes per request                                        | 24 hours                                                |
 | **Concurrency**                    | Single request per instance                                         | Configurable concurrency per instance                               | Not applicable                                          |
-| **Pricing model**                  | Pay based on execution time and invocations                              | Pay based on vCPU and memory usage                                       | Pay based on vCPU and memory usage                           |
+| **Pricing model**                  | Pay based on execution time and invocations                         | Pay based on vCPU and memory usage                                  | Pay based on vCPU and memory usage                      |
 | **Triggers**                       | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | HTTP requests, scheduled (CRONs), messaging events (NATS, SQS, SNS) | Manual invocation or scheduled                          |
 | **Language support**               | Node, PHP, Python, Go, Rust                                         | Any language/runtime within a container                             | Any language/runtime within a container                 |
-| **Infrastructure management**      | Fully managed, handles provisioning and scaling automatically      | Fully managed, handles provisioning and scaling automatically      | Fully managed, abstracts away infrastructure management |
-| **Cold-starts**                    | There may be startup latency on new instances                           | There may be startup latency on new instances                           | Not applicable (jobs starts when scheduled or invoked)   |
+| **Infrastructure management**      | Fully managed, handles provisioning and scaling automatically       | Fully managed, handles provisioning and scaling automatically       | Fully managed, abstracts away infrastructure management |
+| **Cold-starts**                    | There may be startup latency on new instances                       | There may be startup latency on new instances                       | Not applicable (jobs starts when scheduled or invoked)  |
 | **Supports custom containers**     | No, deploy code in supported languages only                         | Yes, deploy any containerized application                           | Yes, deploy any containerized application               |
 | **Long-running processes**         | Not suitable for long running tasks                                 | Not suitable for long running tasks                                 | Ideal for long running processes                        |
 | **Networking**                     | No VPC support at the moment                                        | No VPC support at the moment                                        | No VPC support at the moment                            |
 | **Secret manager integration**     | Only via local secrets                                              | Only via local secrets                                              | Yes                                                     |
-| **Customisable ephemeral storage** | Yes                                                                 | Yes                                                                 | Yes                                                     |
+| **Customizable ephemeral storage** | Yes                                                                 | Yes                                                                 | Yes                                                     |
 | **Scaling from and to zero**       | Yes                                                                 | Yes                                                                 | Not applicable                                          |
 
 ## Details

diff --git a/menu/navigation.json b/menu/navigation.json
@@ -3781,6 +3781,10 @@
                   {
                     "label": "My function fails after too many retries",
                     "slug": "too-many-retries"
+                  },
+                  {
+                    "label": "Tests fail on private functions",
+                    "slug": "tests-fail-on-private-function"
                   }
                 ],
                 "label": "Troubleshooting",
@@ -3838,6 +3842,10 @@
                     "label": "Secure a container",
                     "slug": "secure-a-container"
                   },
+                  {
+                    "label": "Test a container",
+                    "slug": "test-a-container"
+                  },
                   {
                     "label": "Monitor container logs and metrics",
                     "slug": "monitor-container"
@@ -3939,6 +3947,10 @@
                   {
                     "label": "My container stopped working after a redeploy",
                     "slug": "container-stopped-after-redeploy"
+                  },
+                  {
+                    "label": "Tests fail on private containers",
+                    "slug": "tests-fail-on-ùprivate-container"
                   }
                 ],
                 "label": "Troubleshooting",

diff --git a/serverless/containers/how-to/test-a-container.mdx b/serverless/containers/how-to/test-a-container.mdx
@@ -0,0 +1,44 @@
+---
+meta:
+  title: How to test a container
+  description: Instructions for testing your Serverless Containers on Scaleway.
+content:
+  h1: How to test a container
+  paragraph: Instructions for testing your Serverless Containers on Scaleway.
+tags: container serverless test-container
+dates:
+  validation: 2025-01-14
+  posted: 2025-01-15
+categories:
+  - serverless
+---
+
+This page shows you how to execute Serverless Containers from the [Scaleway console](https://console.scaleway.com). The **Test** feature of a container allows you to run your code using a selection of methods to make sure it behaves as expected.
+
+<Macro id="requirements" />
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- [Created a container](/serverless/containers/how-to/deploy-container/)
+
+1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays.
+
+2. Click the relevant containers namespace. A list of your containers displays.
+
+3. Click the name of the container you want to test.
+
+4. Open the **Test** tab.
+
+5. Select the **method** you want to use from the drop-down menu.
+
+6. Enter the **path** to your container. Leave the default `/` value if the host of your container is not located in a specific folder.
+
+7. Click **+ Advanced options** to add any required HTTP header or parameter to your container.
+
+8. Click **Run**.
+
+The **Output** section displays the response from your container and the status code.
+
+<Message type="note">
+If you encounter a message error while testing your container, refer to the [dedicated troubleshooting](/serverless/containers/troubleshooting/tests-fail-on-private-container/) for more information.
+</Message>
diff --git a/serverless/containers/reference-content/containers-billing.mdx b/serverless/containers/reference-content/containers-billing.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Understand billing for Scaleway Serverless Containers.
 tags: containers serverless serverless-containers billing serverless-billing serverless-containers-billing
 dates:
-  validation: 2024-07-02
+  validation: 2025-01-15
   posted: 2023-06-15
 categories:
   - serverless

diff --git a/serverless/containers/reference-content/difference-jobs-functions-containers.mdx b/serverless/containers/reference-content/difference-jobs-functions-containers.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Differences between jobs, functions, and containers in Scaleway.
 tags: job container functions differences vs docker image
 dates:
-  validation: 2024-07-02
+  validation: 2025-01-15
   posted: 2023-12-08
 categories:
   - serverless

diff --git a/serverless/containers/troubleshooting/tests-fail-on private-container.mdx b/serverless/containers/troubleshooting/tests-fail-on private-container.mdx
@@ -0,0 +1,26 @@
+---
+meta:
+  title: Tests fail on private Serverless Containers
+  description: I get error messages when testing private Serverless Containers using the Scaleway Console
+content:
+  h1: Tests fail on private Serverless Containers
+  paragraph: I get error messages when testing private Serverless Containers using the Scaleway Console
+tags: serverless containers private troubleshooting issue error test authentication token unable
+dates:
+  validation: 2025-01-14
+  posted: 2025-01-14
+categories:
+  - serverless
+---
+
+## Problem
+
+I get error messages when testing private Serverless Containers using the Scaleway Console.
+
+### Cause
+
+[Private](/serverless/containers/concepts/#privacy-policy) containers require a `X-Auth-Token` HTTP header when being run or tested.
+
+### Possible solutions
+
+Make sure that you have [created an authentication token](/serverless/containers/how-to/create-auth-token-from-console/) from the Scaleway console, and passed it as a HTTP header while [testing your container](/serverless/containers/how-to/test-a-container).
diff --git a/serverless/functions/how-to/test-a-function.mdx b/serverless/functions/how-to/test-a-function.mdx
@@ -38,3 +38,7 @@ This page shows you how to execute Serverless Functions from the [Scaleway conso
 8. Click **Run**.
 
 The **Output** section displays the response from your function and the status code.
+
+<Message type="note">
+If you encounter a message error while testing your function, refer to the [dedicated troubleshooting](/serverless/functions/troubleshooting/tests-fail-on-private-function/) for more information.
+</Message>
diff --git a/serverless/functions/reference-content/difference-jobs-functions-containers.mdx b/serverless/functions/reference-content/difference-jobs-functions-containers.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Understand the differences between jobs, functions, and containers in Scaleway's serverless platform.
 tags: job container functions differences vs docker image
 dates:
-  validation: 2024-08-05
+  validation: 2025-01-15
   posted: 2024-07-02
 categories:
   - serverless

diff --git a/serverless/functions/troubleshooting/tests-fail-on-private-function.mdx b/serverless/functions/troubleshooting/tests-fail-on-private-function.mdx
@@ -0,0 +1,26 @@
+---
+meta:
+  title: Tests fail on private Serverless Functions
+  description: I get error messages when testing private Serverless Functions using the Scaleway Console
+content:
+  h1: Tests fail on private Serverless Functions
+  paragraph: I get error messages when testing private Serverless Functions using the Scaleway Console
+tags: serverless functions private troubleshooting issue error test authentication token unable
+dates:
+  validation: 2025-01-14
+  posted: 2025-01-14
+categories:
+  - serverless
+---
+
+## Problem
+
+I get error messages when testing private Serverless Functions using the Scaleway Console.
+
+### Cause
+
+[Private](/serverless/functions/concepts/#privacy-policy) functions require a `X-Auth-Token` HTTP header when being run or tested.
+
+### Possible solutions
+
+Make sure that you have [created an authentication token](/serverless/functions/how-to/create-auth-token-from-console/) from the Scaleway console, and passed it as a HTTP header while [testing your function](/serverless/functions/how-to/test-a-function).
diff --git a/serverless/jobs/reference-content/cron-schedules.mdx b/serverless/jobs/reference-content/cron-schedules.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Setting up cron schedules in Scaleway Serverless Jobs.
 tags: serverless jobs cron crontab schedule cronjob
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2023-12-12
 categories:
   - serverless

diff --git a/serverless/jobs/reference-content/deploy-job.mdx b/serverless/jobs/reference-content/deploy-job.mdx
@@ -6,7 +6,7 @@ content:
   h1: Methods to deploy Serverless Jobs
   paragraph: How to deploy a job in Scaleway Serverless Jobs.
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2023-12-20
 ---
 

diff --git a/serverless/jobs/reference-content/difference-jobs-functions-containers.mdx b/serverless/jobs/reference-content/difference-jobs-functions-containers.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Understand differences between jobs, functions, and containers in Scaleway.
 tags: job container functions differences vs docker image
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2023-11-13
 categories:
   - serverless

diff --git a/serverless/sql-databases/how-to/manage-backups.mdx b/serverless/sql-databases/how-to/manage-backups.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Instructions for managing backups in Scaleway serverless SQL databases.
 tags: sql-databases serverless database backup snapshot restore
 dates:
-  validation: 2024-07-02
+  validation: 2025-01-15
   posted: 2023-12-05
 categories:
   - serverless
@@ -69,5 +69,3 @@ Serverless SQL Databases are automatically backed up every day at the same time.
 <Message type="tip">
   You can restore the downloaded backup using the [pg_restore](https://www.postgresql.org/docs/current/app-pgrestore.html) utility.
 </Message>
-
-
diff --git a/storage/object/how-to/delete-an-object.mdx b/storage/object/how-to/delete-an-object.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to delete objects from Object Storage buckets.
 tags: object storage object-storage
 dates:
-  validation: 2024-07-03
+  validation: 2025-10-15
   posted: 2021-05-27
 categories:
   - storage

diff --git a/storage/object/how-to/download-files-from-a-bucket.mdx b/storage/object/how-to/download-files-from-a-bucket.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Download files stored in Scaleway Object Storage buckets.
 tags: download bucket object-storage object storage
 dates:
-  validation: 2024-07-04
+  validation: 2025-01-15
   posted: 2021-05-27
 categories:
   - storage
@@ -21,7 +21,6 @@ categories:
 - An [Object Storage bucket](/storage/object/how-to/create-a-bucket/)
 - An object in your [bucket](/storage/object/how-to/upload-files-into-a-bucket/)
 
-
 1. Click **Object Storage** in the **Storage** section of the side menu. The list of your buckets displays.
 2. Click the name of your selected bucket in the buckets list. A list of your objects displays.
 3. Click <Icon name="download" /> next to the desired object to start the download to your local file system.
diff --git a/storage/object/how-to/monitor-consumption.mdx b/storage/object/how-to/monitor-consumption.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Monitor your Object Storage resource consumption.
 tags: bandwidth consumption metrics logs object storage cockpit
 dates:
-  validation: 2024-06-13
+  validation: 2025-01-15
   posted: 2020-10-09
 categories:
   - storage
@@ -51,5 +51,3 @@ To view your Object Storage metrics and logs, use the Grafana dashboard, which i
 <Message type="note">
   Your Object Storage metrics and logs dashboards are also accessible from the console via the **Metrics** and **Logs** tabs of a bucket.
 </Message>
-
-
diff --git a/storage/object/how-to/use-obj-stor-with-private-networks.mdx b/storage/object/how-to/use-obj-stor-with-private-networks.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Configure and use Object Storage with Private Networks.
 tags: object storage private-networks private network
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2021-05-27
 categories:
   - storage
@@ -79,5 +79,3 @@ You must create an Instance without a flexible IP using the following specificat
 ## Conclusion
 
 You have now configured an Instance with a Private Network to communicate with Scaleway's Object Storage platform using a Public Gateways. The gateway ensures the exchange of data between your Private Network and the public Internet.
-
-
diff --git a/storage/object/troubleshooting/api-key-does-not-work.mdx b/storage/object/troubleshooting/api-key-does-not-work.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Fix issues with non-functional API keys in Object Storage.
 tags: api key bucket object storage aws cli
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2023-12-15
 categories:
   - storage

diff --git a/storage/object/troubleshooting/lost-bucket-access-bucket-policy.mdx b/storage/object/troubleshooting/lost-bucket-access-bucket-policy.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Regain access to buckets lost due to policy issues.
 tags: help troubleshooting bucket access lose policy principal
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2023-12-15
 categories:
   - storage
@@ -84,4 +84,3 @@ If you have the permission to apply a bucket policy, you can also delete it. To
     - User-agent (SDK, client, console, etc.)
     - Transaction ID (if possible)
     - Log / trace of the error (if possible)
-