Jobs - Concepts
Container RegistryLink to this anchor
Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the migration guide for full details.
Environment variablesLink to this anchor
An environment variable is a variable whose value is set outside the program, typically through functionality built into the operating system. An environment variable is made up of a name/value pair, and any number may be created and available for reference at a point in time.
Ephemeral storageLink to this anchor
In addition to CPU and RAM, Serverless Jobs also provide a storage volume for the duration of the task. This storage space allows to hold the data retrieved by the job, and disappears once the execution is complete.
GB-sLink to this anchor
Unit used to measure the resource consumption of a container. It reflects the amount of memory consumed over time.
JobLink to this anchor
Serverless Jobs is a fully managed solution that enables you to plan, schedule, queue and run batch processing workloads without worrying about provisioning and scaling. A job is a single instance of one of these batch processing workloads.
Job definitionLink to this anchor
A Job definition is a template for a Serverless Job. It contains all the information necessary to run the job, including the container image used, the resources allocated, and the command to execute. The definition acts as a blueprint for job runs.
Job nameLink to this anchor
The name of a job is part of the job definition and is used for informational purposes only.
Job runLink to this anchor
A job run is the execution of a job definition. It can be in a running, succeeded, canceled, or failed status. Each job run has a unique identifier and can be individually monitored using Cockpit.
LoggingLink to this anchor
Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources: see monitoring Serverless Jobs.
Maximum durationLink to this anchor
The maximum duration option allows you to define the maximum execution time before your job is automatically killed.
MetricsLink to this anchor
Performance metrics for your Serverless resources are natively available: see monitoring Serverless Jobs.
Private Networks compatibilityLink to this anchor
Refer to the dedicated FAQ for more information on Serverless Jobs compatibility with Private Networks and Virtual Private Cloud (VPC).
Schedule (cron)Link to this anchor
A schedule (cron) is a mechanism used to automatically start a Serverless Job at a specific time on a recurring schedule. It works similarly to a traditional Linux cron job, using the * * * * * format. Refer to our cron schedules reference for more information.
Serverless ContainersLink to this anchor
Serverless Containers is a fully managed service that enables you to run containerized applications in a scalable and serverless environment.
It automatically handles infrastructure management, scaling, and load balancing, allowing you to focus on writing code without worrying about servers or clusters. Serverless Containers supports any language, framework, or binary that can run in a container, and it integrates seamlessly with other Scaleway services, making it ideal for deploying modern, event-driven, and API-based applications.
Serverless FunctionsLink to this anchor
Serverless Functions are fully managed compute services that allow you to run small, stateless code snippets or functions in response to HTTP requests or events.
These functions automatically scale based on demand and are designed to be lightweight, event-driven, and easily deployable, eliminating the need to worry about infrastructure management. Functions is built on top of Serverless Containers, meaning you can run your functions packaged in containers and have them scale efficiently.
Serverless JobsLink to this anchor
Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See the comparison between Serverless products for more information.
Secrets referenceLink to this anchor
A secret reference is a mechanism that allows you to use a secret stored in Secret Manager within Serverless Jobs. It allows you to securely reference sensitive data, such as API secret keys, passwords, tokens, or certificates.
Startup commandLink to this anchor
This optional field allows you to specify a custom command executed upon starting your job if your container image does not have one already, or if you use a public container image.
StatusLink to this anchor
A Serverless Job run can have the following statuses:
- Succeeded: your Serverless Job run finished in a successful state.
- Queued: your Serverless Job run is waiting for resources to run.
- Error: your Serverless Job run finished with an error or timeout. Check our troubleshooting documentation to solve the issue.
- Canceled: your Serverless Job run has been canceled by the user.
StatelessLink to this anchor
Refers to a system or application that does not maintain any persistent state between executions. In a stateless environment, each request or operation is independent, and no information is retained from previous interactions.
This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others.
To store data you can use Scaleway Object Storage, Scaleway Managed Databases, and Scaleway Serverless Databases.
Terraform/OpenTofuLink to this anchor
Terraform/OpenTofu is an infrastructure-as-code tool, owned by Hashicorp. Serverless Jobs integrate easily with your infrastructure as code, via our Terraform/OpenTofu provider and resources.
Examples using Terraform/OpenTofu can be found in our Serverless Examples repository, such as our example using Terraform/OpenTofu with Serverless Jobs.
vCPU-sLink to this anchor
Unit used to measure the resource consumption of a container. It reflects the amount of vCPU used over time.