From 34d9bdd21621c281dd8eb9d995103d50944ab0d5 Mon Sep 17 00:00:00 2001 From: Thomas Tacquet Date: Thu, 11 Dec 2025 14:37:34 +0100 Subject: [PATCH 1/2] fix(jobs): missing permissions to start job --- pages/serverless-jobs/how-to/run-job.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pages/serverless-jobs/how-to/run-job.mdx b/pages/serverless-jobs/how-to/run-job.mdx index 5ecda60e5d..b5fc6a3fae 100644 --- a/pages/serverless-jobs/how-to/run-job.mdx +++ b/pages/serverless-jobs/how-to/run-job.mdx @@ -53,12 +53,14 @@ The **Job runs** section contains basic monitoring information for your jobs: Depending on the settings used, Serverless Jobs can have dependencies on other products, such as: +- **Serverless Jobs**: base product permissions - **Secret Manager**: to securely inject data into jobs - **Container Registry**: to store images of jobs Executing a Serverless Job can fail if some permissions are not definied properly in an [IAM policy](/iam/how-to/create-policy/), for example: +- `ServerlessJobsFullAccess` Is required to start the Job. - If the job definition uses an image from **Container Registry**, add the `ContainerRegistryReadOnly` permission. - If the job definition consumes data from **Secret Manager**, add the `SecretManagerSecretAccess` permission. -Refer to the [dedicated documentation](/serverless-jobs/how-to/monitor-job/) for comprehensive information on how to monitor jobs using Scaleway Cockpit. \ No newline at end of file +Refer to the [dedicated documentation](/serverless-jobs/how-to/monitor-job/) for comprehensive information on how to monitor jobs using Scaleway Cockpit. From 6f4282248bfd6faecc7553049a4470a27a96bdd3 Mon Sep 17 00:00:00 2001 From: Thomas TACQUET Date: Fri, 12 Dec 2025 16:47:17 +0100 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- pages/serverless-jobs/how-to/run-job.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/serverless-jobs/how-to/run-job.mdx b/pages/serverless-jobs/how-to/run-job.mdx index b5fc6a3fae..69421b5f89 100644 --- a/pages/serverless-jobs/how-to/run-job.mdx +++ b/pages/serverless-jobs/how-to/run-job.mdx @@ -57,9 +57,9 @@ Depending on the settings used, Serverless Jobs can have dependencies on other p - **Secret Manager**: to securely inject data into jobs - **Container Registry**: to store images of jobs -Executing a Serverless Job can fail if some permissions are not definied properly in an [IAM policy](/iam/how-to/create-policy/), for example: +Executing a Serverless Job can fail if some permissions are not defined properly in an [IAM policy](/iam/how-to/create-policy/), for example: -- `ServerlessJobsFullAccess` Is required to start the Job. +- `ServerlessJobsFullAccess` is required to start the Job. - If the job definition uses an image from **Container Registry**, add the `ContainerRegistryReadOnly` permission. - If the job definition consumes data from **Secret Manager**, add the `SecretManagerSecretAccess` permission.