scaleway · SamyOubouaziz · Jan 17, 2025 · Jan 15, 2025 · Jan 15, 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/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/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/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/api-cli/bucket-operations.mdx b/storage/object/api-cli/bucket-operations.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Perform various operations on buckets in Scaleway Object Storage using the CLI.
 tags: object storage object-storage bucket
 dates:
-  validation: 2024-07-04
+  validation: 2025-01-15
   posted: 2018-09-14
 categories:
   - storage

diff --git a/storage/object/api-cli/bucket-website-api.mdx b/storage/object/api-cli/bucket-website-api.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Configure bucket websites using the API in Scaleway Object Storage.
 tags: object storage object-storage bucket static-website api
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2021-02-17
 categories:
   - storage
@@ -142,7 +142,9 @@ After setting up the basic bucket website configuration with `put-bucket-website
 
 You can also upload the rest of the static web page files that make up your website.
 
->**Note:** If this is your first time uploading objects into a bucket, you can follow the step-by-step on [this documentation page](/storage/object/how-to/upload-files-into-a-bucket/).
+<Message type="note">
+If this is your first time uploading objects into a bucket, you can follow the step-by-step on [this documentation page](/storage/object/how-to/upload-files-into-a-bucket/).
+</Message>
 
 ### Configuring access
 
@@ -179,12 +181,10 @@ If you want your website to be accessible, you need to set up a bucket policy.
 
 ### Configuring your URL
 
-You can access your website using the website endpoint of your bucket, generated by Amazon S3 under the default format:
+You can access your website using the website endpoint of your bucket, generated by Scaleway Object Storage under the default format:
 
 `https://<bucket_name>.s3-website.<bucket_region>.scw.cloud`
 
 Replace `<bucket_name>` and `<bucket_region>` accordingly.
 
 Alternatively, you can [configure a CNAME Record](/tutorials/s3-customize-url-cname/) for your bucket URL, to be able to access the website through a domain name of your choice.
-
-
diff --git a/storage/object/api-cli/common-operations.mdx b/storage/object/api-cli/common-operations.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Perform common operations efficiently using Scaleway Object Storage CLI.
 tags: object storage object-storage api api-operation getservice
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2018-09-13
 categories:
   - storage

diff --git a/storage/object/api-cli/generate-aws4-auth-signature.mdx b/storage/object/api-cli/generate-aws4-auth-signature.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Generate AWS Signature Version 4 for authentication in Scaleway Object Storage.
 tags: object-storage object storage awsv4 aws authentication
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2018-07-16
 categories:
   - storage
@@ -53,7 +53,7 @@ The canonical request included in the signature is made up of:
 
 This means that the following example:
 
-```
+```sh
 GET /?acl HTTP/1.1
 
 Host: my-bucket.s3.ams-nl.scw.cloud
@@ -63,7 +63,7 @@ x-amz-date: 20190411T101653Z
 
 Would be based on the following canonical code:
 
-```
+```sh
 GET
 /
 acl=
@@ -77,7 +77,7 @@ e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
 
 **Example authorization header**
 
-```
+```sh
 Authorization: AWS4-HMAC-SHA256
 Credential=SCWN63TF9BMCPVNARV5A/20190411/nl-ams/s3/aws4_request,
 SignedHeaders=host;x-amz-acl;x-amz-content-sha256;x-amz-date,
@@ -86,7 +86,7 @@ Signature=6cab03bef74a80a0441ab7fd33c829a2cdb46bba07e82da518cdb78ac238fda5
 
 **Signing example (pseudo code)**
 
-```
+```sh
 canonicalRequest = `
 ${HTTPMethod}\n
 ${canonicalURI}\n
@@ -108,5 +108,3 @@ signingKey = HMAC-SHA256(dateRegionServiceKey, "aws4_request")
 
 signature = Hex(HMAC-SHA256(signingKey, stringToSign))
 ```
-
-
diff --git a/storage/object/api-cli/installing-minio-client.mdx b/storage/object/api-cli/installing-minio-client.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Install and configure the MinIO client for Scaleway Object Storage.
 tags: object-storage object storage minio mc minio-client
 dates:
-  validation: 2024-07-04
+  validation: 2025-01-15
   posted: 2021-08-25
 categories:
   - storage
@@ -18,10 +18,9 @@ The [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc.html) (`mc
 
 <Macro id="requirements" />
 
-- [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
+- [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.
 
-
-1. Follow the instructions given in the [official MinIO documentation](https://min.io/docs/minio/linux/reference/minio-mc.html#id3) to install the MinIO client (`mc`) for your OS.
+1. Follow the instructions given in the [official MinIO documentation](hhttps://min.io/docs/minio/linux/reference/minio-mc.html#install-mc) to install the MinIO client (`mc`) for your OS.
     <Message type="note">
     Make sure that you download the binary somewhere that is in your `$PATH`.
     </Message>
@@ -30,7 +29,7 @@ The [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc.html) (`mc
     ```
     mc alias set <ALIAS> <YOUR-S3-ENDPOINT> <YOUR-ACCESS-KEY> <YOUR-SECRET-KEY> --api <API-SIGNATURE>
     ```
-    For example, if your Scaleway Object Storage endpoint is in the `nl-ams` region, you can use the following command (replace the two fields in pointy brackets with your access key and secret key):
+    For example, if your Scaleway Object Storage endpoint is in the `nl-ams` region, you can use the following command (replace the two placeholders with your access key and secret key):
     ```
     mc alias set s3 https://s3.nl-ams.scw.cloud <YOUR-ACCESS-KEY> <YOUR-SECRET-KEY> --api S3v4
     ```
@@ -57,4 +56,3 @@ The [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc.html) (`mc
         ```
         mc --help
         ```
-
diff --git a/storage/object/api-cli/manage-bucket-permissions-ip.mdx b/storage/object/api-cli/manage-bucket-permissions-ip.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Manage bucket permissions based on IP addresses in Scaleway Object Storage.
 tags: object storage bucket ip permission
 dates:
-  validation: 2024-07-03
+  validation: 2025-01-15
   posted: 2021-05-18
 categories:
   - storage
@@ -56,49 +56,8 @@ In the example below, we allow the `192.0.2.0/24` IP range to perform the `s3:Li
   ]
 }
 ```
-You can have the same result if you `Deny` actions for IP addresses specified under the `NotIpAddress` condition:
-```json
-{
-  "Version": "2023-04-17",
-  "Id": "MyBucketPolicy",
-  "Statement": [
-    {
-      "Sid": "Grant List and GET from my Instances",
-      "Effect": "Deny",
-      "Principal": "*",
-      "Action": ["s3:ListBucket", "s3:GetObject"],
-      "Resource": ["<BUCKET_NAME>", "<BUCKET_NAME>/*"],
-      "Condition": {
-        "NotIpAddress": {
-          "aws:SourceIp": "198.51.100.0/24"
-        }
-      }
-    }
-  ]
-}
-```
-Alternatively, you can block certain IP addresses or IP address ranges from performing actions on your bucket. You can also use `NotIpAddress` with the `Allow` Effect:
-```json
-{
-  "Version": "2023-04-17",
-  "Id": "MyBucketPolicy",
-  "Statement": [
-    {
-      "Sid": "Grant List and GET from my Instances",
-      "Effect": "Allow",
-      "Principal": "*",
-      "Action": ["s3:ListBucket", "s3:GetObject"],
-      "Resource": ["<BUCKET_NAME>", "<BUCKET_NAME>/*"],
-      "Condition": {
-        "NotIpAddress": {
-          "aws:SourceIp": "2001:db8::/32"
-        }
-      }
-    }
-  ]
-}
-```
-Or the `Deny` effect paired with the `IpAddress` condition:
+
+Alternatively, you can block certain IP addresses or IP address ranges from performing actions on your bucket:
 ```json
 {
   "Version": "2023-04-17",