Ajinkya Atiwadkar
11/24/2025, 7:21 AMkapa.ai
11/24/2025, 7:21 AMyaml apiVersion: v1 kind: Secret metadata: name: airbyte-config-secrets type: Opaque stringData: aws-secret-manager-access-key-id: "<YOUR_AWS_ACCESS_KEY_ID>" aws-secret-manager-secret-access-key: "<YOUR_AWS_SECRET_ACCESS_KEY>" Airbyte expects this secret by default under the name airbyte-config-secrets with the above keys.[\[Platform secrets\]](https://docs.airbyte.com/platform/deploying-airbyte/integrations/secrets) 2. Configure the Helm values for AWS Secrets Manager (chart v2) In your values.yaml that Argo CD will apply: yaml global: secretsManager: type: AWS_SECRET_MANAGER secretName: "airbyte-config-secrets" # the secret created above awsSecretManager: region: "<aws-region>" # e.g. us-east-1 authenticationType: credentials # or instanceProfile tags: # optional - key: team value: deployments - key: business-unit value: engineering kms: "" # optional KMS key ARN This is the v2 chart form of the configuration.[\[Platform values\]](https://docs.airbyte.com/platform/deploying-airbyte/integrations/secrets#values) 3. Apply via Argo CD - Put the above values.yaml in your Git repo. - Configure your Argo CD Application to use the Airbyte Helm chart and this values.yaml. - Ensure the airbyte-config-secrets secret exists in the same namespace before Argo CD syncs Airbyte. 4. Important behavior Changing the connector secret storage configuration later will cause all existing connectors to fail; you’ll need to recreate them so they read from AWS Secrets Manager.[\[Platform values\]](https://docs.airbyte.com/platform/deploying-airbyte/integrations/secrets#values)