Cloud Key Management Service VS Azure Key Vault

If you're using GCP, look at KMS. If you're deploying to a VM/GKE/Cloud Functions you can add an identity to the VM/pod/function respectively and grant IAM permissions such that the machine account can fetch credentials. Source: about 1 year ago

You should check out Google's Cloud KMS platform. It's specifically built for managing keys and may be a better fit for your use case. Source: over 1 year ago

This makes private keys more sensitive than your average application secret, so storing them in plaintext in a dot-env file in a server where half the dev team has ssh access is not a good idea. It is key (pun intended) to leverage key management solutions that can keep the key safely stored. There are managed cloud-based options, such as GCP KMS or AWS KMS, self-managed like Hashi Vault, and even hardware... - Source: dev.to / over 1 year ago

Have a look at https://aws.amazon.com/kms/ or https://cloud.google.com/security-key-management. Source: over 1 year ago

GCP Cloud Key Management Service (KMS) is a cloud-hosted key management service that allows you to manage symmetric and asymmetric encryption keys for your cloud services in the same way as onprem. It lets you create, use, rotate, and destroy AES 256, RSA 2048, RSA 3072, RSA 4096, EC P256, and EC P384 encryption keys. - Source: dev.to / over 2 years ago

Utilize specialized tools like AWS Secrets Manager, HashiCorp Vault,  or Azure Key Vault for secrets management in your serverless environments. These tools keep sensitive data out of function code and configurations and bring advanced features to the table:. - Source: dev.to / 18 days ago

Azure Key Vault is a cloud-based service provided by Microsoft Azure that enables secure storage and management of secrets. It integrates well with Kubernetes, allowing organizations to centralize and control access to secrets within their Azure infrastructure. - Source: dev.to / 5 months ago

No Azure Key Vault[0]? Oh #1 is your product? #3 and #4 mention your product being better? It's your company? Shm [0]: https://azure.microsoft.com/en-us/products/key-vault/. - Source: Hacker News / 5 months ago

Ideally, all secrets should be stored and accessible by a secret manager (Azure Key Vault) and stored on repository only reference to right secret. On the other hand, the developer needs to use the secret's values on their configuration files (i.e. appSettings.json), so a fast way for retrieve them from Key Vault should be nice. - Source: dev.to / 10 months ago

From there, you should be able to use something like GCP HSM or Azure Key Vault (seem to be cheap enough): Https://cloud.google.com/kms/docs/hsm Https://azure.microsoft.com/en-us/products/key-vault/. Source: 11 months ago