New to this? You don’t need to know Kubernetes or Terraform. Qovery sets up Scaleway Object Storage in your cloud account and manages it for you: you fill in a form, or paste the prompt below into your coding agent. The values it publishes, listed under Outputs, reach your other services as environment variables. Qovery tells you when a newer version of the Blueprint is available. Check the requirements in the Reference section before you start, and try it first in a development environment.
Open the environment, then New service › Blueprint.
Find Scaleway Object Storage in the catalog and pick the major version.
Fill in the variables. Required ones are marked; the others use their defaults.
Create the service, and deploy it now or later.
List the catalog to get the latest tag, then create the service from it. qovery api signs the requests with your CLI session.
ORG_ID="REPLACE_WITH_ORGANIZATION_ID"ENV_ID="REPLACE_WITH_ENVIRONMENT_ID"qovery api "organization/$ORG_ID/blueprint/catalog" | jq '.. | objects | select(.name? == "scaleway-object-storage")'cat > blueprint.json <<'EOF'{ "name": "scaleway-object-storage", "tag": "SCW/object-storage/default/1.1.9", "icon": "app://qovery-console/scaleway", "variables": [ { "name": "bucket_name", "value": "REPLACE_WITH_BUCKET_NAME" } ], "spec_overrides": { "engine_version": "1.9.7" }}EOFBLUEPRINT_ID=$(qovery api "environment/$ENV_ID/blueprint" --method POST --input - < blueprint.json | jq -r .id)rm blueprint.json # it can hold secret valuesqovery api "blueprint/$BLUEPRINT_ID/deploy" --method POSTqovery api "blueprint/$BLUEPRINT_ID" # status of the latest deployment
Replace each REPLACE_WITH_ value. Add optional variables to variables the same way.
Paste this into Claude Code, Cursor, Codex or another coding agent with the Qovery agent skills installed (curl -fsSL https://skill.qovery.com/install.sh | bash).
Prompt
Add the Qovery Blueprint Scaleway Object Storage (scaleway-object-storage) to one of my Qovery environments and deploy it. Ask me for bucket_name.Ask me before deploying to a production environment.Docs: https://www.qovery.com/docs/configuration/blueprints/scaleway-object-storage.md
You don’t add any file to your repository. Qovery creates the Blueprint from the Console or the API.
Generated from qbm.yml at SCW/object-storage/default/1.1.9, the manifest the Console form is built from.
All 4 variables
Name
Type
Required
Default
Secret
Description
bucket_name
string
Yes
Globally unique, auto-lowercased: 3–63 letters, digits or hyphens, starting and ending with a letter or digit. No underscores.
acl
string
private
Bucket ACL
versioning_enabled
bool
false
Enable object versioning
force_destroy
bool
false
Allow bucket deletion even if it contains objects
Outputs become environment variables that other services in the environment can use. By default Qovery also creates an alias for each output, prefixed with the Blueprint’s name; see Aliases Qovery creates for outputs for the naming rules and the cases where no alias is created.
From the Blueprint’s README.Creates a Scaleway Object Storage bucket with configurable ACL, versioning, and force-destroy options. The bucket name is automatically lowercased before creation. Bucket names are globally unique across all Scaleway regions.
Globally unique bucket name. Auto-lowercased. 3–63 chars; letters, digits, and hyphens only; must start and end with a letter or digit. Underscores are not allowed.
acl
string
no
private
Bucket ACL: private, public-read, or public-read-write.
Scaleway IAM permissions are granted via permission sets on a policy attached to the application/user whose API key is used.Attach a policy with the following permission sets, scoped to the target Project:
Permission set
Why
ObjectStorageFullAccess
Create / read / update / delete the bucket, including ACL, versioning, and tags.
ProjectReadOnly
Resolve the project context for the API call.
The minimum scope is the Project where Qovery deploys this blueprint. If your cluster has its own project, attach the policy there.When force_destroy = true, the same ObjectStorageFullAccess set also covers object-level deletes during teardown.
