Paul
05/14/2026, 12:19 AMkapa.ai
05/14/2026, 12:20 AMvalues.yaml file under the global.secretsManager (or secretsManager) section. Look for a block like this:
global:
secretsManager:
type: AWS_SECRET_MANAGER # or GOOGLE_SECRET_MANAGER, AZURE_KEY_VAULT, VAULT
secretName: "airbyte-config-secrets"
awsSecretManager:
region: <aws-region>
authenticationType: credentials
If this section is absent or enabled: false, no external secrets manager is configured and Airbyte defaults to storing secrets in the database (in plain text). [Secret Management]
2. Check your Kubernetes Secret The credentials for the secrets manager are stored in a Kubernetes secret (typically named airbyte-config-secrets). You can inspect it with:
kubectl get secret airbyte-config-secrets -n <YOUR_NAMESPACE> -o yaml
The presence of keys like aws-secret-manager-access-key-id, gcp.json, or azure-key-vault-client-id indicates which secrets manager (if any) has been configured. [Preconfiguring Kubernetes Secrets]
3. Verify via the Cloud Provider Console After configuration, Airbyte creates a test secret in your secrets manager. You can verify it appeared by checking:
• AWS: AWS Secrets Manager in your specified region (look for the AirbyteManaged=true tag)
• GCP: Google Cloud Secret Manager
• Azure: Azure Key Vault secrets
[Verification Steps]
4. If using abctl (local installs) For local deployments managed by abctl, you can check the status of your installation with:
abctl local status
This shows the deployed Helm chart version and app version, but to see the full configuration you would need to review the values.yaml file you passed during install. [abctl]
> Note: Modifying the secrets manager configuration after initial setup will cause all existing connectors to fail, so it's important to confirm the configuration before making changes. [Secret Management] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.