Provision a Timescale Cloud (TimescaleDB/Postgres) service with configurable CPU, memory, and HA replicas, via the Timescale Terraform provider
Qovery creates it in your account with a third-party provider, using credentials you enter in the form, as a Blueprint service in one of your environments.
New to this? You don’t need to know Terraform or Kubernetes. Qovery sets up Timescale Cloud Service in your account with the provider: 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 Timescale Cloud Service 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? == "timescale-cloud-service")'cat > blueprint.json <<'EOF'{ "name": "timescale-cloud-service", "tag": "EXTERNAL/timescale-cloud/default/1.0.7", "icon": "app://qovery-console/timescaledb", "variables": [ { "name": "timescale_project_id", "value": "REPLACE_WITH_TIMESCALE_PROJECT_ID" }, { "name": "timescale_access_key", "value": "REPLACE_WITH_TIMESCALE_ACCESS_KEY", "is_secret": true }, { "name": "timescale_secret_key", "value": "REPLACE_WITH_TIMESCALE_SECRET_KEY", "is_secret": true }, { "name": "service_name", "value": "REPLACE_WITH_SERVICE_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 Timescale Cloud Service (timescale-cloud-service) to one of my Qovery environments and deploy it. Ask me for timescale_project_id, timescale_access_key, timescale_secret_key and service_name.Ask me before deploying to a production environment.Docs: https://www.qovery.com/docs/configuration/blueprints/timescale-cloud-service.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 EXTERNAL/timescale-cloud/default/1.0.7, the manifest the Console form is built from.
All 8 variables
Name
Type
Required
Default
Secret
Description
timescale_project_id
string
Yes
Timescale Cloud project ID
timescale_access_key
string
Yes
Yes
Timescale Cloud client credentials - access key
timescale_secret_key
string
Yes
Yes
Timescale Cloud client credentials - secret key
service_name
string
Yes
1–128 chars
region_code
string
us-east-1
AWS-style code, e.g. us-east-1, eu-west-1
milli_cpu
number
500
CPU in milli-CPU; must pair with memory_gb
memory_gb
number
2
Memory in GB; must pair with milli_cpu (500m/2GB, 1000m/4GB, …)
ha_replicas
number
0
High-availability replicas, 0–2
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.
All 6 outputs
Name
Secret
Description
service_id
Timescale service ID
hostname
Service hostname
port
Service port
username
Master database username
password
Yes
Master database password
connection_uri
Yes
PostgreSQL URI with credentials (database tsdb, TLS required)
Secret variables and outputs are encrypted and masked in Qovery, but Terraform can also keep their values, and values derived from them, in its state. With the Qovery-managed state backend (the default), Qovery stores the state. If you use your own backend, protect it and keep state files out of version control.
From the Blueprint’s README.Provisions a Timescale Cloud service (timescale_service) — managed TimescaleDB/PostgreSQL — via the official timescale/timescale provider (~> 2.0).
Timescale Cloud only (managed SaaS), not self-hosted TimescaleDB.
