Skip to content

chore(serverless): concepts general update #6171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
thomas-tacquet wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chore(serverless): concepts general update #6171

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
30c37d4
chore(serverless): concepts general update
thomas-tacquet Feb 9, 2026
c95b07e
note about cockpit pricing
thomas-tacquet Feb 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion pages/serverless-containers/concepts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,6 +107,10 @@ Environment variables are key/value pairs injected into your container. They are

Some names are reserved. [See details about reserved names](/serverless-containers/reference-content/containers-limitations/#configuration-restrictions).

If a variable is defined in both your `Dockerfile` and Servlerless Containers service, the Serverless Containers configuration takes precedence.

For sensitive information we encourage to use [Secret environment variables](/serverless-containers/concepts/#secrets).
Copy link
Collaborator

@jcirinosclwy jcirinosclwy Feb 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For sensitive information we encourage to use [Secret environment variables](/serverless-containers/concepts/#secrets).
For sensitive information, we encourage you to use [Secret environment variables](/serverless-containers/concepts/#secrets).


## Ephemeral storage

In addition to vCPU and RAM, Serverless Containers also provide a storage volume for the duration of the task. This storage space allows you to hold data during the life of the Servlerless Container instance and disappears once the execution is complete.
Expand Down Expand Up @@ -223,7 +227,7 @@ Refer to the [dedicated documentation](/serverless-containers/reference-content/

## Secrets

Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. Secrets defined at the container level override the ones defined at the namespace level if they have the same name.
Secrets are an extra-secure type of [environment variable](/serverless-containers/concepts/#environment-variables). They are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. Secrets defined at the container level override the ones defined at the namespace level if they have the same name.

Secrets on Serverless Containers are not linked with Secret Manager product yet.

Expand Down
2 changes: 2 additions & 0 deletions pages/serverless-containers/how-to/monitor-container.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ import Requirements from '@macros/iam/requirements.mdx'

Scaleway Serverless Containers is fully integrated into [Cockpit](/cockpit/quickstart/), and allows you to quickly access your logs and metrics. This page explains how to get started with Scaleway Cockpit to monitor your Serverless Containers.

Logs and metrics for Serverless Containers with default retention (31 days for metrics / 7 days for logs & traces) are free of charge.

<Requirements />

- A Scaleway account logged into the [console](https://console.scaleway.com)
Expand Down
44 changes: 23 additions & 21 deletions pages/serverless-containers/reference-content/containers-concurrency.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,32 +9,34 @@ tags: serverless containers concurrency concurrent execution scaling parallelism

## Concurrency overview

Concurrency determines the number of incoming requests a single instance of a container can process before scaling up. Serverless Containers automatically scale according to the number of instances needed to handle the incoming workload.
Concurrency determines the number of incoming requests a single instance of a container can process before scaling up. Serverless Containers automatically scale according to the number of instances needed to handle the incoming workload.

Unlike Serverless Functions which handles only one request per instance, Serverless Containers is designed to handle multiple requests simultaneously within one container. This is a powerful feature for optimizing performance and reducing costs.
Copy link
Collaborator

@jcirinosclwy jcirinosclwy Feb 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Unlike Serverless Functions which handles only one request per instance, Serverless Containers is designed to handle multiple requests simultaneously within one container. This is a powerful feature for optimizing performance and reducing costs.
Unlike Serverless Functions, which handles only one request per instance, Serverless Containers is designed to handle multiple requests simultaneously within one container. This is a powerful feature for optimizing performance and reducing costs.


A higher number of instances processing requests at the same time implies a greater usage of memory and [vCPU](/serverless-containers/concepts/#vcpu), and consequently a higher cost.

```
Concurrency = 1
┌─────────────┐
│ ┌──────┐│
│ │ │ ││
└─────┼───► │ ││ Concurrency = 80
│ │ ││
│ └──────┘│ ┌─────────────┐
│ ┌──────┐│ │ │ ┌──────┐│
│ │ ││ └────┼───► │ ││
3 requests ──────┼───► │ ││ 3 requests ─────┼───► │ ││
│ │ ││ ┌────┼───► │ ││
│ └──────┘│ │ │ └──────┘│
│ ┌──────┐│ └─────────────┘
│ │ ││ 1 service
Concurrency = 1

┌─────────────┐
│ ┌──────┐│
│ │ │ ││
└─────┼───► │ ││ Concurrency = 80
│ │ ││
│ └──────┘│ ┌─────────────┐
│ ┌──────┐│ │ │ ┌──────┐│
│ │ ││ └────┼───► │ ││
3 requests ──────┼───► │ ││ 3 requests ─────┼───► │ ││
│ │ ││ ┌────┼───► │ ││
│ └──────┘│ │ │ └──────┘│
│ ┌──────┐│ └─────────────┘
│ │ ││ 1 service
┌─────┼───► │ ││ 1 container instance
│ │ │ ││
│ └──────┘│
└─────────────┘
1 service
3 container instances
│ │ │ ││
│ └──────┘│
└─────────────┘
1 service
3 container instances
```

## Concurrency setting
Expand Down
4 changes: 3 additions & 1 deletion pages/serverless-functions/concepts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,8 @@ Environment variables are key/value pairs injected into your function. They are

Some names are reserved. [See details on reserved names](/serverless-functions/reference-content/functions-limitations/#configuration-restrictions).

For sensitive information we encourage to use [Secret environment variables](/serverless-functions/concepts/#secrets).
Copy link
Collaborator

@jcirinosclwy jcirinosclwy Feb 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For sensitive information we encourage to use [Secret environment variables](/serverless-functions/concepts/#secrets).
For sensitive information, we encourage you to use [Secret environment variables](/serverless-functions/concepts/#secrets).


## GB-s

Unit used to measure the resource consumption of a Serverless Function. It reflects the amount of memory consumed over time.
Expand Down Expand Up @@ -190,7 +192,7 @@ When provisioned with a [minimum scale](#min-scale) of `0`, Serverless Functions

## Secrets

Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation.
Secrets are an extra-secure type of [environment variable]((/serverless-functions/concepts/#environment-variables). They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation.
Copy link
Collaborator

@jcirinosclwy jcirinosclwy Feb 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Secrets are an extra-secure type of [environment variable]((/serverless-functions/concepts/#environment-variables). They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation.
Secrets are an extra-secure type of [environment variable](/serverless-functions/concepts/#environment-variables). They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation.


Secrets defined at the function level override the ones defined at the namespace level if they have the same name.

Expand Down
2 changes: 2 additions & 0 deletions pages/serverless-functions/how-to/monitor-function.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ import Requirements from '@macros/iam/requirements.mdx'

Scaleway Serverless Functions is fully integrated into [Cockpit](/cockpit/quickstart/), and allows you to quickly access your logs and metrics. This page explains how to get started with Scaleway Cockpit to monitor your Serverless Functions.

Logs and metrics for Serverless Jobs with default retention (31 days for metrics / 7 days for logs & traces) are free of charge.

<Message type="tip">
Use your Cockpit logs and metrics to fine-tune the resources allocated to your Serverless Functions to avoid bottlenecks and over-provisioning.
</Message>
Expand Down
2 changes: 2 additions & 0 deletions pages/serverless-jobs/how-to/monitor-job.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ import Requirements from '@macros/iam/requirements.mdx'

You can monitor the activity of your Serverless Jobs using the [Scaleway console](https://console.scaleway.com) to check the current status, RAM, and CPU consumption of your runs. Also, Serverless Jobs is fully integrated into Scaleway’s Observability [Cockpit](/cockpit/quickstart/), and allows you to quickly access your logs.

Logs and metrics for Serverless Jobs with default retention (31 days for metrics / 7 days for logs & traces) are free of charge.

<Requirements />

- A Scaleway account logged into the [console](https://console.scaleway.com)
Expand Down
Loading