Skip to main content
This feature is available on:
  • AWS Managed Cluster
  • GCP Managed Cluster
Supported Secrets Providers:
  • AWS Secrets Manager
  • AWS Parameter Store
  • GCP Secret Manager

How it works

Qovery integrates with external secrets by deploying ESO (External Secrets Operator) in your cluster.

Configure a Secret Manager Access

You can configure a Secret Manager Access in the Add-ons section of your cluster.
Overview add Secret Manager Access
Creating or Editing a Secret Manager Access requires the cluster to be redeployed
Select the guide for your secrets provider:

AWS Secrets Manager

Connect to AWS Secrets Manager from an AWS or GCP cluster

AWS Parameter Store

Connect to AWS Parameter Store from an AWS or GCP cluster

GCP Secret Manager

Connect to GCP Secret Manager from a GCP or AWS cluster

Reference the external secrets in your service

Once your cluster is deployed, you can link external secrets to any service:
  • Open your service
  • Navigate to the Variables tab
  • Select the External secrets tab
  • Click Add external secret
External Secrets path
Qovery automatically lists the secrets available in your Secrets Provider to simplify setup:
External Secrets list secrets available
You can filter results by prefix to narrow the list:
External Secrets list secrets available by prefix
To create an external secret, you need to:
  • Select the Secret Manager Access
  • Select the secret from your Secret Manager
  • Provide the environment variable key to inject
External Secrets details
External secrets are fetched only at deployment. A running service won’t automatically pick up changes to its external secrets — it requires a redeploy.

Using external secrets with Terraform services

Terraform services handle environment variables differently from other service types. Unlike application services where any environment variable is directly injected into the container, Terraform services expose variables through the Terraform variable system (TF_VAR_*). This means external secrets require a specific naming convention to be picked up correctly by Terraform at runtime. External secrets are supported only in the “External Secrets” tab:
  • You can’t reference an external secret inside the “Terraform variables” section
  • You can’t reference an external secret inside the “Terraform arguments” section
To inject external secrets into your Terraform workflows:
  • The key of your external secrets must follow the pattern TF_VAR_${your_variable}
  • You must not have an override of your_variable inside the “Terraform variables” from any file.tfvars
Terraform service external secret
Setting external secrets at the environment level multiplies cloud costs.You can set external secrets at the environment level, but be careful:
  • The secret value will be fetched individually for each service running in the environment.
  • With many services, this multiplies the number of secret fetches and can significantly increase your cloud costs.
Prefer service-level secrets when only a subset of services need access to the value.