secrets-store-csi-driver-provider-aws
The AWS provider for the Secrets Store CSI Driver allows you to fetch secrets from AWS Secrets Manager and AWS Systems Manager Parameter Store, and mount them into Kubernetes pods. (by aws)
secrets-store-csi-driver
Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume. (by kubernetes-sigs)
Our great sponsors
| secrets-store-csi-driver-provider-aws | secrets-store-csi-driver | |
|---|---|---|
| 6 | 22 | |
| 422 | 1,174 | |
| 2.8% | 2.1% | |
| 6.9 | 8.5 | |
| 8 days ago | 5 days ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
secrets-store-csi-driver-provider-aws
Posts with mentions or reviews of secrets-store-csi-driver-provider-aws.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-15.
- AWS secret store CSI Driver provider - how to reload pod after SecretProvider update?
-
Shhhh... Kubernetes Secrets Are Not Really Secret!
The driver can also sync changes to secrets. The driver currently supports Vault, AWS, Azure, and GCP providers. Secrets Store CSI Driver can also sync provider secrets as Kubernetes secrets; if required, this behavior needs to be explicitly enabled during installation.
-
Secrets Management on Kubernetes: How do you handle it?
Great suggestions below. If you are a AWS shop and use secrets manager you can use https://github.com/aws/secrets-store-csi-driver-provider-aws
-
A better way to manage secrets: reference an external secret defined in the cloud provider environment (please support the idea or give your feedback)
AWS SS-CSI driver
-
Airflow setup/environment and best practices
For a secrets manager we use the aws secrets store csi driver to fetch our secrets from aws secrets manager and parameter store. On Azure we still need to implement something similar, however an implementation does exist we haven't gotten around to it yet ;)
-
Moving structure to kubernetes, question about secrets and credentials
secrets-store-csi-driver-provider-aws
secrets-store-csi-driver
Posts with mentions or reviews of secrets-store-csi-driver.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-19.
-
Check your secrets into Git [video]
I'm not a fan of this approach. I think the Secrets Store CSI Driver (https://secrets-store-csi-driver.sigs.k8s.io/) has a better approach.
-
EKS secrets - Bitnami sealed secrets or KMS?
Secret Store CSI Driver is what we're playing with now. Pretty excellent.
-
How does your company do secret management? AWS/GCP/Azure/Vault/CyberArk etc. thoughts?
If you deploy on k8s, keep your eye on https://secrets-store-csi-driver.sigs.k8s.io/
- K8s secret management
-
Secret Management in Kubernetes: Approaches, Tools, and Best Practices
Considering the major limitations of using Kubernetes Secrets, there are many new approaches being developed by the Kubernetes community. Kubernetes SIGs like the Secrets Store CSI Driver and solutions like the external secrets operator that works with third-party secret managers, and options to seal secrets through tools like bitnami’s sealed-secrets. To skip the tools and move directly to best practices, click here.
-
Azure AKS/Container App can't access Key vault using managed identity
Just to clarify, CSI secret driver is from cncf not Microsoft. Only msft piece is the portion that integrates with key vault. https://secrets-store-csi-driver.sigs.k8s.io/
-
Vault Secrets in K8S, use CRD Injector ?
https://secrets-store-csi-driver.sigs.k8s.io/ and https://developer.hashicorp.com/vault/tutorials/kubernetes/kubernetes-secret-store-driver
-
Shhhh... Kubernetes Secrets Are Not Really Secret!
The Secrets Store CSI Driver is a native upstream Kubernetes driver that can be used to abstract where the secret is stored from the workload. If you want to use a cloud provider's secret manager without exposing the secrets as Kubernetes Secret objects, you can use the CSI Driver to mount secrets as volumes in your pods. This is a great option if you use a cloud provider to host your Kubernetes cluster. The driver supports many cloud providers and can be used with different secret managers.
-
SealedSecrets or external secret operator?
If you want security they are both bad, use something like the secret manager of your choice API directly in your app or https://secrets-store-csi-driver.sigs.k8s.io/ this will keep the actual secrets out of etcd and env vars and give you more security
- Secrets Management on Kubernetes: How do you handle it?
What are some alternatives?
When comparing secrets-store-csi-driver-provider-aws and secrets-store-csi-driver you can also consider the following projects:
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
secrets-store-csi-driver-provider-vault - HashiCorp Vault Provider for Secret Store CSI Driver [Moved to: https://github.com/hashicorp/vault-csi-provider]
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
k3d - Little helper to run CNCF's k3s in Docker
secrets-store-csi-driver-provider-azure - Azure Key Vault provider for Secret Store CSI driver allows you to get secret contents stored in Azure Key Vault instance and use the Secret Store CSI driver interface to mount them into Kubernetes pods.
external-secrets - External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
helm - The Kubernetes Package Manager
ingress-nginx - Ingress-NGINX Controller for Kubernetes
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
secrets-store-csi-driver-provider-aws vs secrets-store-csi-driver-provider-gcp
secrets-store-csi-driver vs kubernetes-external-secrets
secrets-store-csi-driver-provider-aws vs secrets-store-csi-driver-provider-vault
secrets-store-csi-driver vs argocd-vault-plugin
secrets-store-csi-driver-provider-aws vs k3d
secrets-store-csi-driver vs secrets-store-csi-driver-provider-gcp
secrets-store-csi-driver-provider-aws vs secrets-store-csi-driver-provider-azure
secrets-store-csi-driver vs external-secrets
secrets-store-csi-driver-provider-aws vs helm
secrets-store-csi-driver vs ingress-nginx
secrets-store-csi-driver-provider-aws vs kind
secrets-store-csi-driver vs sealed-secrets