Cloud Key Management Service Reviews and details

Social recommendations and mentions

• Where to store credentials?

  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

• Wait... can I just reference PEM files stored in Secret Manager directly from a Cloud Run instance??

  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

• A case for secure web3 operations

  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

• How to store private key on a VPS in a secure manner?

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

• GCP security best practices

  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

• client_secrets.json in production ?

  Use a key management system like Google's Cloud Key Management or AWS KMS. Source: over 2 years ago