Skip to navigationSkip to main contentSkip to footerScaleway DocsSparklesIconAsk our AI
SparklesIconAsk our AI
ProfileOutlineIcon Log inSign up

Injected environment variables

The following standardized Scaleway environment variables are injected by default in the Job runs to improve and optimize data management.

Variable nameDescriptionSample value
$SCW_SLS_RESOURCE_IDID of the Job run00000000-0000-0000-0000-000000000000
$SCW_SLS_PARENT_IDID of the Job definition00000000-0000-0000-0000-000000000000
$SCW_SLS_RESOURCE_NAMEName of the Job run"job-name"
$SCW_SLS_PROJECT_IDID of the Project of the Job00000000-0000-0000-0000-000000000000
$SCW_SLS_ORGANIZATION_IDID of the Organization of the Job00000000-0000-0000-0000-000000000000
$SCW_SLS_CPUvCPU limit of the Job run560
$SCW_SLS_RAMMemory limit of the Job run1024
$SCW_SLS_EPHEMERAL_STORAGEEphemeral storage limit of the Job run1000
$SCW_SLS_IMAGEImage of the Job runscaleway/cli:latest
$SCW_SLS_REGIONRegion of the Job runfr-par
InformationOutlineIcon
Note

It is not possible to use any other environment variable key that starts with SCW_SLS, regardless of case. Refer to the Jobs limitations documentation page for more information.

Environment variables priority

When the same environment variable is injected by multiple sources, the Scaleway infrastructure follows a precedence rule to determine the value for that variable.

The order of precedence, from highest to lowest is the following.

  1. Environment variables defined in your command-line environment.

  2. Static variables (i.e. variables set in a Terraform/OpenTofu configuration file).

  3. Variables defined in the Scaleway SDK configuration file or Scaleway CLI configuration file.

Still need help?

Create a support ticketArrowRightIcon
SearchIcon
No Results