AWS Secrets Manager vs. Google Cloud Key Management

[AWS Secrets Manager] is really good at managing the secrets for each environment (stage, production, ...), and with a simple command, the users will get all the variables for running the project. Depending on the user role, they could just read and/or edit the variables on the Secrets Manager on AWS. This facilitates the management of the secrets.

Incentivized

Use for most types of cloud SQL services. Excellent modern-day encryption technologies. If a customer wants to manage their keys then Google Cloud Platform is well suited for those people if it matters. Able to divide workloads and pipelines. Customer managed encryption keys support for Data fusion, Data Proc, Cloud SQL, and GKE. We use Cloud EKM: key use operations $0.03 per 10,000 operations for our day to day operations.

Incentivized

• Single source of truth for secrets
• Securely share secrets with colleagues
• Securely store secrets for services to access during runtime

Incentivized

• Option for Customer-Managed Encryption keys for Cloud which very [few] providers do.
• Option to enhance security via Hardware Security Modules.
• Easy control panel and CLI.
• Unified commands to approve or deny key requests.

Incentivized

• It could be good if a user can use a variable in the project but can't see them in the manager on AWS

Incentivized

• They removed the option for RSA128 bit security so yeah if it matters it a bummer.
• Pipelines are limited and very [few] for the amount you pay.
• General usability and Rapid CI/CD.

Incentivized

Both AWS Secrets Manager & MS Azure Key Vault are pretty similar. They're the default secrets manager on their respective cloud platform.

The choice comes down to where your infra resides on.

Incentivized

The UI / UX, first of all, is night and day difference. The main attraction after the services were this: It's user friendly. It welcomes new users and properly guides them on what to do and what you can expect. Honestly, I had a very bad experience with Microsoft Azure in 2018, so I think the Google Cloud Key Management service is best for me for now and I may give the new Azure a try later.

Incentivized

• Costs are suitable
• ROI is positive

Incentivized

• There is no Return of investment in our operations as we use it for KMS.
• The only ROI is that we have a piece of mind while our data is handled by Google.
• Our main objective is being fulfilled and the staff as well as customer are happy.
• Value for money.

Incentivized