-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Airbyte should support external secret stores #837
Comments
FYI this is handled in Airflow and i guess commonly used so if we switch/integrate somehow, this could benefit from it too: |
+1 Nice to have an alternative secrets backend, even just the Hashicorp vault will be better.
Helps in Automating secrets management end to end. |
+1 plugable secret store |
Not sure if it's under consideration, but, If possible, reading from existing stores would be huge benefit. In our case we have a different flow keeping our tokens up-to-date elsewhere since we use them as well for different use cases in our product so simply mentioning a way to read from existing external stores would be nice. Happy to work with Airbyte on any/all part of it. |
Would be great if it can read from env variables too. |
+1 - this is an important security capability |
look like you can use the |
Hi, any updates / estimates on this? We would like to run Airbyte OSS on Kubernetes, but unencrypted secrets is a big security hazard for us. Environment variables or HashiCorp Vault would suit us the best. |
+1 this would be really helpful ! |
FWIW. This is an interesting project as well for folks wanting to expose secrets in K8s. It sort of provides the abstraction layer, so you dont necessarily write code for each vaulting system. It is something we are looking to utilize internally in our own k8s infrastructure. https://github.com/kubernetes-sigs/secrets-store-csi-driver |
We support GCP secrets store and AWS secrets manager. It is possible to add other external secrets stores. |
Hey it looks like you guys support writing to a secrets store for any secrets, however, how do I set airbyte to read a secret from an existing secret store. More specifically, I'm setting up a source that requires and API key, and I don't want to have my team type that API key in, I would like for them to just state the name of the secret in the secret store |
We've had a request to add CyberArk secret support from a customer in a support case, Feature request for this at: #32981 |
Has anyone integrated Airbyte with Azure KeyVault for storing key/pwd/uid info securely? This could be a blocker for us to use Airbyte. |
Hi Team, To follow up on previous question on Key Vault , does any one integrated Key Vault? if yes any reference link. |
Using AWS Systems Manager with encrypted params is also way cheaper than AWS Secrets Manager |
Tell us about the problem you're trying to solve
I would like Airbyte to store connector secrets in external secret stores (HashiCorp Vault, AWS Secrets Manager, GCS Secrets Manager...)
Target Secret Stores
The text was updated successfully, but these errors were encountered: