diff --git a/pages/block-storage/api-cli/managing-a-volume.mdx b/pages/block-storage/api-cli/managing-a-volume.mdx index 12c0263998..7f4269c8da 100644 --- a/pages/block-storage/api-cli/managing-a-volume.mdx +++ b/pages/block-storage/api-cli/managing-a-volume.mdx @@ -7,7 +7,7 @@ content: paragraph: Master Block Storage with our comprehensive guide. Learn to format, mount, transfer data, and expand partitions efficiently. Perfect for all skill levels. tags: volume block-storage block mount format use dates: - validation: 2024-12-06 + validation: 2025-06-09 posted: 2019-11-29 categories: - block-storage @@ -20,7 +20,6 @@ This documentation only explains how to mount **additional block volumes to your - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - An [Instance](/instances/concepts/#instance) - [Attached](/block-storage/how-to/attach-a-volume/) an additional Block Storage volume to your Instance @@ -29,7 +28,6 @@ This documentation only explains how to mount **additional block volumes to your In order to mount and use your Block Storage volume, you need to connect to the Instance it is attached to, via SSH. Then, check that the volume is available, format it, and mount it following the instructions below. - ### Verifying device availability 1. Connect to your Instance with `ssh`. @@ -41,8 +39,7 @@ Then, check that the volume is available, format it, and mount it following the lsblk ``` - - You should see an output similar to the following. The root Block volume `sda`, runs your OS. The Block volume named `sdb` is the one we will be mounting to the Instance. + You should see an output similar to the following. The root Block volume `sda`, contains your OS. The Block volume named `sdb` is the one we will be mounting to the Instance. ```sh no-copy root@scw-festive-agnesi:~# lsblk @@ -58,8 +55,6 @@ Then, check that the volume is available, format it, and mount it following the The Scaleway ecosystem uses [GB](https://en.wikipedia.org/wiki/Gigabyte) to define storage sizes and not [GiB](https://en.wikipedia.org/wiki/Gibibyte) as the default on linux. ---- - ### Formatting the Block volume Formatting your volume prepares it for storing files. @@ -100,19 +95,19 @@ Formatting your volume prepares it for storing files. Once you have created your file system, you need to define where you want to mount your volume, and create a mount point (directory) for it. -1. Create the mount point. Feel free to replace `block-volume` with another name for your mount point. +1. Create the mount point. You can replace `block-volume` with another name for your mount point. ``` mkdir /mnt/block-volume ``` 2. Mount the volume. We recommend that you use the `defaults` option, as in the command below. ``` - # Make sure that you replace sdX with the name of your volume + # Replace sdX with the name of your volume mount -o defaults /dev/sdX /mnt/block-volume ``` If you want to see all available options, you can run `man mount` on your Instance. -3. Run the following command to check if your file system was properly mounted: +3. Run the following command to check if your volume was properly mounted: ``` lsblk ``` @@ -147,14 +142,14 @@ echo "UUID=$(blkid --output value /dev/sdX | head -n1) /mnt/block-volume ext4 de ### Transferring data from your local machine to the remote Block volume -You may wish to transfer files from your local machine to your Instance's remote Block volume. This can be achieved with [rsync](https://en.wikipedia.org/wiki/Rsync), a tool for efficiently transferring and copying files. The rsync utility is pre-installed on most Linux distributions and macOS. +You can transfer files from your local machine to your Instance's remote Block volume with [rsync](https://en.wikipedia.org/wiki/Rsync), a tool for efficiently transferring and copying files. The rsync utility is pre-installed on most Linux distributions and macOS. 1. Check that rsync is installed on your local machine with the following command: ``` rsync --version ``` - You should see an output similar to the following: + An output similar to the following displays: ```sh no-copy rsync version 3.1.3 protocol version 31 @@ -176,14 +171,18 @@ You may wish to transfer files from your local machine to your Instance's remote - For Linux CentOS/ Fedora, you can use the YUM package manager: `sudo yum install rsync`. - On Mac OSX with the Homebrew package manager, you can use `brew install rsync`. + 2. On your local machine, open a new terminal and use the following command to create a file called `hello-world.txt`: ``` nano hello-world.txt ``` 3. Enter the text `Hello World!`. -4. Press `Ctrl O`, `Enter`, and `Ctrl X` to save and exit the file. + +4. Press `Ctrl+O`, then `Enter`, then `Ctrl+X` to save and exit the file. + 5. Enter the following command to transfer the file to your Instance's mounted block volume. Ensure that you use your own Instance's IP address: + ``` rsync -a hello-world.txt root@:/mnt/block-volume ``` @@ -194,16 +193,18 @@ The file is now transferred. You can connect to your Instance again, and use the ## Increasing the partition size of the volume with growpart +`growpart` allows you to resize partitions. If you have increased the size of the partition's underlying volume, for example, you can increase the size of the partition to make use of the additional space. + - - We recommend that you make a backup of your data using the [snapshot](/block-storage/how-to/create-a-snapshot/) feature, before increasing the partition size of your volume. This helps you avoid any potential data loss. - - You need to have partitioned your volume to follow the procedure below - - If the partition you want to resize is mounted, you need to [unmount it](/block-storage/api-cli/unmounting-a-volume/) beforehand + - Make sure to make a backup of your data using the [snapshot](/block-storage/how-to/create-a-snapshot/) feature beforehand to avoid any potential data loss + - You must have partitioned your volume to follow the procedure below + - If the partition you want to resize is mounted, you must [unmount it](/block-storage/api-cli/unmounting-a-volume/) beforehand -`growpart` allows you to resize partitions. If you have increased the size of the partition's underlying volume, for example, you might want to increase the size of the partition to make use of the additional space. - 1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). + 2. Use the `lsblk` command to identify your volume partition. Ensure that the partition is **not mounted before you resize it**. In the following example, we are resizing `sdb1`: + ``` root@scw-festive-agnesi:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS @@ -216,20 +217,19 @@ The file is now transferred. You can connect to your Instance again, and use the ``` 3. Use `growpart` to increase the partition size of your Block Storage volume (here `sdb1`): + ``` # Replace /dev/sdX 1 with the name of your partition growpart /dev/sdX 1 ``` - - Make sure that you add a space between the device identifier (`/dev/sdX`) and the partition number (`1`). - + An output similar to the following displays: - You should see an output similar to the following: ``` CHANGED: partition=1 start=0 old: size=39061504 end=39061504 new: size=58490880 end=58490880 ``` -4. Use `lsblk` to check that the partition was correctly resized. In the following output, you can see in the `SIZE` field that our partition `sbd1` went from `18.6G` (step 2) to `27.9G`. + +4. Use `lsblk` to check that the partition was correctly resized. In the following output, you can see that our partition `sbd1` went from `18.6G` (step 2) to `27.9G`. ``` root@scw-festive-agnesi:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS diff --git a/pages/block-storage/api-cli/unmounting-a-volume.mdx b/pages/block-storage/api-cli/unmounting-a-volume.mdx index 939d2c5479..0d31960939 100644 --- a/pages/block-storage/api-cli/unmounting-a-volume.mdx +++ b/pages/block-storage/api-cli/unmounting-a-volume.mdx @@ -7,38 +7,37 @@ content: paragraph: Learn how to safely unmount a Block Storage volume from your Instance, and ensure data integrity. tags: volume block-storage block unmount dates: - validation: 2024-12-06 + validation: 2025-06-09 posted: 2023-11-23 categories: - block-storage - storage --- - ## Unmounting a Block Storage volume - Unmounting a volume means detaching it from the operating system so it is no longer accessible. You can do this if you want to stop using it, prevent data corruption, or plan to [detach it](/block-storage/how-to/detach-a-volume/) from your Instance and attach it to another. This page shows you how to unmount a volume from the operating system using the `umount` command. + - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created an [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - Created an [Instance](/instances/how-to/create-an-instance/) with an additional Block Storage volume +1. Open a terminal and use the following command to [connect to your Instance](/instances/how-to/connect-to-instance/). Make sure that you replace `` with your Instance's IP. You can also find the SSH command in your Instance's **Overview** tab in the Scaleway console. -1. Open a terminal and use the following command to connect to your Instance. Make sure that you replace `` with your Instance's IP. You can also find the SSH command in your Instance's **Overview** tab in the Scaleway console. ``` ssh root@ ``` -2. Use `lsblk` to check where your volume is mounted. You should see an output similar to the following: + +2. Run the `lsblk` command to check where your volume is mounted. You should see an output similar to the following: ``` root@scw-heuristic-shtern:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdb 8:0 0 18.6G 0 disk /mnt/block-volume ``` -3. Unmount the volume to remove it from your current setup. Replace `/mnt/block-volume` with your mount point. +3. Run the command below to unmount the volume to remove it from your current setup. Replace `/mnt/block-volume` with your mount point. ``` umount /mnt/block-volume ``` @@ -48,9 +47,7 @@ Unmounting a volume means detaching it from the operating system so it is no lon NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdb 8:0 0 18.6G 0 disk ``` - - Remember to edit the `/etc/fstab` file and delete the line corresponding to your block volume if you have used [Persistent Mounting](/block-storage/api-cli/managing-a-volume/#using-fstab-for-persistent-mounting). - -Refer to the [dedicated documentation](/block-storage/api-cli/managing-a-volume/) for more information about managing your Block Storage volumes. +5. If you have used [Persistent Mounting](/block-storage/api-cli/managing-a-volume/#using-fstab-for-persistent-mounting), edit the `/etc/fstab` file and delete the line corresponding to your block volume. +Your Block Storage volume is now unmounted from your Instance. Refer to the [dedicated documentation](/block-storage/api-cli/managing-a-volume/) for more information about managing your Block Storage volumes. diff --git a/pages/block-storage/concepts.mdx b/pages/block-storage/concepts.mdx index 3f4ee08eb9..f2a294d0c0 100644 --- a/pages/block-storage/concepts.mdx +++ b/pages/block-storage/concepts.mdx @@ -7,7 +7,8 @@ content: paragraph: Explore essential concepts of Block Storage, including block devices, IOPS, SANs, local volumes, and their roles in enhancing storage performance and reliability. tags: block storage volumes concept dates: - validation: 2024-11-13 + validation: 2025-06-09 + posted: 2023-11-23 categories: - block-storage - storage @@ -19,7 +20,7 @@ A block device is a storage volume on a network-connected storage system that is ## IOPS -IOPS or Input/Ouptut Operations Per Second, is a unit of measurement that indicates how many input or output operations a storage device is performing per second. +IOPS or Input/Ouptut Operations Per Second, is a unit of measurement that indicates how many read/write operations a storage device is performing per second. Scaleway Block Storage Low Latency offers two IOPS limits: diff --git a/pages/object-storage/api-cli/combining-iam-and-object-storage.mdx b/pages/object-storage/api-cli/combining-iam-and-object-storage.mdx index 749fe71d83..a89c926146 100644 --- a/pages/object-storage/api-cli/combining-iam-and-object-storage.mdx +++ b/pages/object-storage/api-cli/combining-iam-and-object-storage.mdx @@ -7,7 +7,7 @@ content: paragraph: Integrate IAM with Scaleway Object Storage for enhanced access control. tags: object storage command bucket amazon-s3 iam permissions acl policy dates: - validation: 2024-11-27 + validation: 2025-06-12 posted: 2023-01-17 categories: - storage diff --git a/pages/object-storage/api-cli/enable-sse-c.mdx b/pages/object-storage/api-cli/enable-sse-c.mdx index 97ccd6a41f..d3f9f69c05 100644 --- a/pages/object-storage/api-cli/enable-sse-c.mdx +++ b/pages/object-storage/api-cli/enable-sse-c.mdx @@ -7,7 +7,7 @@ content: paragraph: Enable server-side encryption with customer-provided keys (SSE-C) in Scaleway. tags: object storage server side encryption sse sse-c cli s3 dates: - validation: 2024-11-12 + validation: 2025-06-12 posted: 2024-05-30 categories: - storage diff --git a/pages/object-storage/concepts.mdx b/pages/object-storage/concepts.mdx index 0a787920ef..5f4c8ca80c 100644 --- a/pages/object-storage/concepts.mdx +++ b/pages/object-storage/concepts.mdx @@ -7,7 +7,8 @@ content: paragraph: Understand key concepts and features of Scaleway Object Storage. tags: retention endpoint object-storage storage bucket acl multipart object amazon-s3 retention signature versioning archived dates: - validation: 2024-11-27 + validation: 2025-06-09 + posted: 2021-05-26 categories: - storage - object-storage @@ -90,7 +91,7 @@ A multipart upload consists of three steps: - The client initiates the upload to a specific bucket - The different parts are uploaded -- Object Storage constructs the object from the uploaded parts +- Object Storage builds the object from the uploaded parts ## Object @@ -116,7 +117,7 @@ Parts are the chunks of data that compose multipart objects. ## Prefix -A prefix is a string of characters at the beginning of the [object key name](#object). They are often used to organize your data similarly to directories and to manage object [lifecycle](#lifecycle-configuration). However, prefixes are not directories. +A prefix is a string of characters at the beginning of the [object key name](#object). They are often used to organize your data similarly to directories, and to manage object [lifecycle](#lifecycle-configuration). However, prefixes are not directories. In the context of Scaleway Object Storage, prefixes are used to display folders in the Scaleway console for practical reasons. The `/` character in a prefix is used as a delimiter to allow you to organize your objects hierarchically. diff --git a/pages/object-storage/how-to/create-bucket-policy.mdx b/pages/object-storage/how-to/create-bucket-policy.mdx index c50509173e..1d5128f8d5 100644 --- a/pages/object-storage/how-to/create-bucket-policy.mdx +++ b/pages/object-storage/how-to/create-bucket-policy.mdx @@ -7,7 +7,7 @@ content: paragraph: Create and apply bucket policies for Object Storage. tags: bucket policy bucket console object storage aws-s3 access dates: - validation: 2024-11-05 + validation: 2025-06-09 posted: 2024-05-30 categories: - storage diff --git a/pages/object-storage/reference-content/supported-checksums.mdx b/pages/object-storage/reference-content/supported-checksums.mdx index 19579017d1..c17b4ff6bd 100644 --- a/pages/object-storage/reference-content/supported-checksums.mdx +++ b/pages/object-storage/reference-content/supported-checksums.mdx @@ -7,7 +7,7 @@ content: paragraph: Discover the checksums supported by Scaleway Object Storage. tags: object storage checksum supported aws object integrity dates: - validation: 2024-11-14 + validation: 2025-06-09 posted: 2024-11-14 categories: - network diff --git a/pages/scaleway-sdk/go-sdk.mdx b/pages/scaleway-sdk/go-sdk.mdx index 306bc5b2d7..0805104bc2 100644 --- a/pages/scaleway-sdk/go-sdk.mdx +++ b/pages/scaleway-sdk/go-sdk.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to install and use the Scaleway Go software development kit (SDK) tags: devtools sdk go-sdk go golang dates: - validation: 2024-11-27 + validation: 2025-06-09s posted: 2023-11-14 categories: - devtools diff --git a/pages/scaleway-sdk/js-sdk.mdx b/pages/scaleway-sdk/js-sdk.mdx index c869b57364..1e44e77657 100644 --- a/pages/scaleway-sdk/js-sdk.mdx +++ b/pages/scaleway-sdk/js-sdk.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to install and use the Scaleway JS software development kit (SDK) tags: devtools sdk go-sdk scaleway-sdk go golang dates: - validation: 2024-11-27 + validation: 2025-06-09 posted: 2023-11-14 categories: - devtools diff --git a/pages/scaleway-sdk/python-sdk.mdx b/pages/scaleway-sdk/python-sdk.mdx index d55162746f..a13462271c 100644 --- a/pages/scaleway-sdk/python-sdk.mdx +++ b/pages/scaleway-sdk/python-sdk.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to install and use the Scaleway Python software development kit (SDK) tags: devtools sdk python-sdkscaleway-sdk dates: - validation: 2024-11-27 + validation: 2025-06-09 posted: 2023-11-14 categories: - devtools diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index e1cf28eef0..464d515b24 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -7,7 +7,7 @@ content: paragraph: Key concepts of Scaleway Serverless Containers. tags: containers cold-start concurrency container-registry environment-variables jwt vcpu serverless scale autoscaling dates: - validation: 2024-11-14 + validation: 2025-05-26 categories: - serverless --- @@ -138,15 +138,15 @@ The Serverless infrastructure manages incoming request traffic. In scenarios lik ## Logging -Serverless Containers offers a built-in logging system based on Cockpit to track the activity of your resources: see [monitoring Serverless Containers](/serverless-containers/how-to/monitor-container/). +Serverless Containers offers a built-in logging system based on Cockpit to track the activity of your resources. Refer to [monitoring Serverless Containers](/serverless-containers/how-to/monitor-container/) for more information. ## Max scale -This parameter sets the maximum number of container instances. You should adjust it based on your container's traffic spikes, keeping in mind that you may wish to limit the max scale to manage costs effectively. +This parameter sets the maximum number of container instances. You should adjust it based on your container's traffic spikes, keeping in mind that you may wish to limit the maximum scale to manage costs effectively. ## Metrics -Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Containers](/serverless-containers/how-to/monitor-container/). +Performance metrics for your Serverless resources are natively available. Refer to [monitoring Serverless Containers](/serverless-containers/how-to/monitor-container/) for more information. ## Min scale @@ -188,7 +188,7 @@ Refer to the [dedicated FAQ](/serverless-containers/faq/#how-can-i-configure-acc A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/queues/concepts/#scaleway-queues), and invokes the container automatically whenever a message is added to the queue. For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter. -The container can then process the message and perform any required actions, such as updating a database or sending a notification. +The container can then process the message, and perform any required actions, such as updating a database or sending a notification. ## Registry endpoint @@ -204,11 +204,10 @@ Use cases: ## Rolling update -When deploying a new version of a Serverless Container, a rolling update is applied by default. This means that the new version of the service is gradually rolled out to your users without downtime. -Here is how it works: +When deploying a new version of a Serverless Container, a rolling update is applied by default. The new version of the service is gradually rolled out to your users without downtime, as follows: * When a new version of your container is deployed, the platform automatically starts routing traffic to it incrementally, while still serving requests from the old version until the new one is fully deployed. -* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime. +* Once the new version is successfully running, the platform gradually shifts all traffic to it, ensuring zero downtime. * The old version is decommissioned once the new version is fully serving traffic. This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to it. @@ -223,7 +222,7 @@ Refer to the [dedicated documentation](/serverless-containers/reference-content/ ## Scale to zero -One of the advantages of Serverless Containers is that when your container is not triggered, it does not consume any resources, which enables great savings. +When provisioned with a [minimum scale](#min-scale) of `0`, Serverless Containers scale down to zero active instances as long as they are not triggered. While idling, they do not consume any resources, which allows to reduce the cost of your infrastructure. ## Secrets diff --git a/pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx b/pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx index 31ac6f17f6..7d57c4f671 100644 --- a/pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx +++ b/pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx @@ -7,7 +7,7 @@ content: paragraph: Create, manage, and delete namespaces in Scaleway Serverless Containers. tags: container namespace manage create delete environment variable secret dates: - validation: 2024-11-14 + validation: 2025-05-27 posted: 2021-05-26 categories: - serverless @@ -26,10 +26,15 @@ This page shows you how to create and manage a Serverless Containers namespace. 1. Click **Containers** in the **Serverless** section of the side menu. The list of your containers namespaces displays. 2. Click **Create namespace**. If you have no existing Serverless Containers resources in your current Project, click **Deploy container**. 3. Complete the following steps in the wizard: +<<<<<<< MTA-6082 + - Enter a **name** or use the automatically generated one. The name must only contain alphanumeric characters and dashes. + - Enter an optional **description** and **tags**. +======= - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - Optionally, add a **description** and **tags**. +>>>>>>> main - Choose a **region**, which is the geographical location in which your namespace will be deployed. - - Enter any **environment variables** required for your namespace. Environment variables configured in a namespace will be available in all containers/apps within the same namespace. For each environment variable, click **+Add new variable** and enter the key / value pair. + - Enter any **environment variables** required for your namespace. Environment variables configured in a namespace will be available in all containers/apps within the same namespace. For each environment variable, click **+ Add new variable** and enter the key / value pair. - Set secret environment variables (optional). **Secrets** are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**. - Verify the **estimated cost**. 4. Click **Create namespace only** to finish, or click **Create namespace and add container** if you want to [deploy a container](/serverless-containers/how-to/deploy-container/) next. diff --git a/pages/serverless-containers/reference-content/dns-query-rate-limit.mdx b/pages/serverless-containers/reference-content/dns-query-rate-limit.mdx index 1494f93fd3..cc2735f175 100644 --- a/pages/serverless-containers/reference-content/dns-query-rate-limit.mdx +++ b/pages/serverless-containers/reference-content/dns-query-rate-limit.mdx @@ -7,7 +7,7 @@ content: paragraph: Information on how the DNS query rate limiting works with Scaleway Serverless Containers. tags: serverless containers dns query rate limiting limit response dates: - validation: 2024-11-12 + validation: 2025-05-27 posted: 2024-11-12 categories: - serverless diff --git a/pages/serverless-containers/reference-content/use-cases.mdx b/pages/serverless-containers/reference-content/use-cases.mdx index da621d33e7..ddf3bfc06d 100644 --- a/pages/serverless-containers/reference-content/use-cases.mdx +++ b/pages/serverless-containers/reference-content/use-cases.mdx @@ -7,7 +7,7 @@ content: paragraph: Explore use cases for Scaleway Serverless Containers. tags: Containers serverless use-cases dates: - validation: 2024-11-27 + validation: 2025-06-09 posted: 2023-04-24 categories: - serverless diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx index 336c087bb2..33f2a43281 100644 --- a/pages/serverless-functions/concepts.mdx +++ b/pages/serverless-functions/concepts.mdx @@ -7,7 +7,7 @@ content: paragraph: Learn the core concepts and principles behind Scaleway's Serverless Functions. tags: functions cold-start environment-variables gbs jwt handler serverless concept definition dates: - validation: 2024-11-14 + validation: 2025-05-27 categories: - serverless --- @@ -28,11 +28,11 @@ Once the Function is built into an image, it will be pushed to [Container Regist Cold Start is the time a function takes to handle a request when it is called for the first time. The startup process steps are: -* Downloading the container image (which contains the built Function) to our infrastructure +* Downloading the container image (which contains the built function) to our infrastructure * Starting the container and the runtime * Waiting for the container to be ready. -[How to reduce cold starts](/serverless-functions/faq/#how-to-reduce-cold-start-of-serverless-functions) +Refer to the dedicated FAQ on [how to reduce cold starts](/serverless-functions/faq/#how-to-reduce-cold-start-of-serverless-functions) for more information. ## Concurrency @@ -40,7 +40,7 @@ Concurrency defines the capacity of a resource to process several requests at th ## Container Registry -Container Registry is the place where the images of your Serverless Functions are stored before being deployed. +[Container Registry](/container-registry/) is the place where the images of your Serverless Functions are stored before being deployed. ## CRON trigger @@ -80,15 +80,15 @@ The Serverless infrastructure manages incoming request traffic. In scenarios lik ## Logging -Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources: see [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/). +Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources. Refer to [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/) for more information. ## Max scale -This parameter sets the maximum number of function instances. You should adjust it based on your function's traffic spikes, keeping in mind that you may wish to limit the max scale to manage costs effectively. +This parameter sets the maximum number of function instances. You should adjust it based on your function's traffic spikes, keeping in mind that you may wish to limit the maximum scale to manage costs effectively. ## Metrics -Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/)). +Performance metrics for your Serverless resources are natively available. Refer to [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/) for more information. ## Min scale @@ -119,7 +119,7 @@ Refer to the [dedicated FAQ](/serverless-functions/faq/#how-can-i-configure-acce A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/queues/concepts/#scaleway-queues), and invokes the function automatically whenever a message is added to the queue. -For each message that is sent to a queue, the trigger reads the message and invokes the associated function with the message as the input parameter. +For each message that is sent to a queue, the trigger reads the message, and invokes the associated function with the message as the input parameter. The function can then process the message and perform any required actions, such as updating a database or sending a notification. ## Request timeout @@ -136,7 +136,7 @@ When deploying a new version of a Serverless Function, a rolling update is appli Here is how it works: * When a new version of your function is deployed, the platform automatically starts routing traffic to the new version incrementally, while still serving requests from the old version until the new one is fully deployed. -* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime. +* Once the new version is successfully running, the platform gradually shifts all traffic to it, ensuring zero downtime. * The old version is decommissioned once the new version is fully serving traffic. This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to them. @@ -155,7 +155,7 @@ Refer to the [dedicated documentation](/serverless-functions/reference-content/f ## Scale to zero -One of the advantages of Serverless Functions is that when your function is not triggered, it does not consume any resources, which allows for significant savings. +When provisioned with a [minimum scale](#min-scale) of `0`, Serverless Functions scale down to zero active instances as long as they are not triggered. While idling, they do not consume any resources, which allows to reduce the cost of your infrastructure. ## Secrets diff --git a/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx b/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx index 18568aea0b..5946cba0d1 100644 --- a/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx +++ b/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx @@ -7,7 +7,7 @@ content: paragraph: Step-by-step process for creating, managing, and deleting a Serverless Functions namespace in Scaleway. tags: functions namespace create manage delete environment variable secret dates: - validation: 2024-11-14 + validation: 2025-06-09 posted: 2021-05-26 categories: - serverless @@ -30,7 +30,7 @@ This page shows you how to create, manage, and delete a Functions namespace usin 3. Complete the following steps in the wizard: - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - - Optionally, add a **description** and **tags**. + - Enter an optional **description** and **tags**. - Choose a **region**, which is the geographical location in which your namespace will be deployed. - Click **+ Add advanced options** to define any **environment variables** you want to inject into your function. For each environment variable, click **+ Add variable** and enter the key/value pair. - Set optional secret environment variables. **Secrets** are environment variables which are injected into your function and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**. diff --git a/pages/serverless-functions/reference-content/dns-query-rate-limit.mdx b/pages/serverless-functions/reference-content/dns-query-rate-limit.mdx index 9aee0ccffa..3f01a700b0 100644 --- a/pages/serverless-functions/reference-content/dns-query-rate-limit.mdx +++ b/pages/serverless-functions/reference-content/dns-query-rate-limit.mdx @@ -7,7 +7,7 @@ content: paragraph: Information on how the DNS query rate limiting works with Scaleway Serverless Functions. tags: serverless functions dns query rate limiting limit response dates: - validation: 2024-11-12 + validation: 2025-06-09 posted: 2024-11-12 categories: - serverless diff --git a/pages/serverless-functions/reference-content/use-cases.mdx b/pages/serverless-functions/reference-content/use-cases.mdx index 70c4f0e0c9..8945d9cee8 100644 --- a/pages/serverless-functions/reference-content/use-cases.mdx +++ b/pages/serverless-functions/reference-content/use-cases.mdx @@ -7,7 +7,7 @@ content: paragraph: Explore use cases for Scaleway Serverless Functions in various scenarios. tags: functions serverless use-cases dates: - validation: 2024-11-27 + validation: 2025-06-09 posted: 2023-04-24 categories: - serverless diff --git a/pages/serverless-functions/troubleshooting/function-in-error-state.mdx b/pages/serverless-functions/troubleshooting/function-in-error-state.mdx index 773de5a27d..5151f2f18e 100644 --- a/pages/serverless-functions/troubleshooting/function-in-error-state.mdx +++ b/pages/serverless-functions/troubleshooting/function-in-error-state.mdx @@ -7,7 +7,7 @@ content: paragraph: Troubleshoot issues with Scaleway Serverless Functions being in an error state. tags: serverless functions troubleshooting issue error state failed fail dates: - validation: 2024-11-06 + validation: 2025-06-09 posted: 2024-11-06 categories: - serverless @@ -15,11 +15,11 @@ categories: ## Problem -My Serverless Function is in an error state following its execution. +My Serverless Function is in an **error** state following its execution. ## Cause -This error is returned when the function cannot start due to insufficient provisioned resources. +Functions enter the **error** status when they cannot start due to insufficient provisioned resources. ## Possible solution diff --git a/pages/serverless-jobs/concepts.mdx b/pages/serverless-jobs/concepts.mdx index 169b580260..e582074f47 100644 --- a/pages/serverless-jobs/concepts.mdx +++ b/pages/serverless-jobs/concepts.mdx @@ -7,7 +7,8 @@ content: paragraph: Key concepts of Scaleway Serverless Jobs. tags: jobs serverless-jobs definition glossary execution run dates: - validation: 2024-11-14 + validation: 2025-06-09 + posted: 2023-11-07 categories: - serverless --- diff --git a/pages/serverless-jobs/how-to/run-job.mdx b/pages/serverless-jobs/how-to/run-job.mdx index 898d6dbbc5..3ebd13b882 100644 --- a/pages/serverless-jobs/how-to/run-job.mdx +++ b/pages/serverless-jobs/how-to/run-job.mdx @@ -7,7 +7,7 @@ content: paragraph: Learn how to run jobs in Scaleway Serverless platform efficiently. tags: run execute start serverless job scaleway contextual-options parameters dates: - validation: 2024-11-27 + validation: 2025-06-09 posted: 2023-11-14 categories: - serverless diff --git a/pages/serverless-jobs/how-to/stop-job.mdx b/pages/serverless-jobs/how-to/stop-job.mdx index fd6e326e14..a43fbfec38 100644 --- a/pages/serverless-jobs/how-to/stop-job.mdx +++ b/pages/serverless-jobs/how-to/stop-job.mdx @@ -7,7 +7,7 @@ content: paragraph: Discover methods to stop jobs running on Scaleway Serverless. tags: stop execute abort start serverless job scaleway dates: - validation: 2024-11-27 + validation: 2025-06-09 posted: 2023-12-12 categories: - serverless diff --git a/pages/serverless-jobs/quickstart.mdx b/pages/serverless-jobs/quickstart.mdx index 3bc2e86f44..cdca8c7c26 100644 --- a/pages/serverless-jobs/quickstart.mdx +++ b/pages/serverless-jobs/quickstart.mdx @@ -7,7 +7,7 @@ content: paragraph: Get started with Scaleway Serverless Jobs quickly and easily. tags: jobs serverless namespace dates: - validation: 2024-11-27 + validation: 2025-06-09 posted: 2023-11-07 categories: - serverless @@ -42,7 +42,7 @@ Discover the Serverless Jobs interface in the Scaleway console. - Select the **Scaleway** Container Registry. - Select the appropriate **Registry namespace** from the drop-down list, then select the desired **container** and **tag**. - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - - Enter a **description** (optional). + - Enter a **description** and **tags** (optional). - Select the region in which your job will be created. - Choose the smallest **resources** available to allocate to your job. - Set the following startup command in the **Advanced options**: diff --git a/pages/serverless-sql-databases/concepts.mdx b/pages/serverless-sql-databases/concepts.mdx index 4e5ffb2374..69a86c79b9 100644 --- a/pages/serverless-sql-databases/concepts.mdx +++ b/pages/serverless-sql-databases/concepts.mdx @@ -7,7 +7,7 @@ content: paragraph: Detailed explanation of concepts and architecture behind Scaleway's serverless SQL databases. tags: sql databases serverless dates: - validation: 2024-11-14 + validation: 2025-05-26 categories: - serverless --- diff --git a/pages/terraform/quickstart.mdx b/pages/terraform/quickstart.mdx index 143df4ad69..59111d36d4 100644 --- a/pages/terraform/quickstart.mdx +++ b/pages/terraform/quickstart.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to install and configure Terraform/OpenTofu with Scaleway as a provider tags: devtools terraform tf scaleway-provider scaleway-terraform dates: - validation: 2024-11-27 + validation: 2025-06-09 posted: 2023-10-24 categories: - devtools