3 ms·

This is fine if you're committed to using (say) AWS KMS for your encryption needs as a service with its per-API-call pricing. The costs of that obviously scale

This is fine if you're committed to using (say) AWS KMS for your encryption needs as a service with its per-API-call pricing. The costs of that obviously scale in a completely different way from the per-key storage costs (which are actually zero, I think).

CiPHPerCoder 6y ago
If you use the AWS Encryption SDK, you can cache your data keys and reduce your calls to KMS: https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/implement-caching.html https://docs.aws.amazon.com/encryption-sdk/latest/developer-...
kevindong 6y ago
Google's KMS pricing structure is $0.06/key/month + $0.03/10,000 encrypts/decrypts [0]. At $0.06/key/month, that's practically free for most reasonable use cases. For example, if there's 10k secrets that's $7,200/year. If you encrypt/decrypt your secrets 1 million times per day (~11.6 times/s), the access charges would be $1,095/year (1 million operations/day * 365 days/year * $0.03 / 10,000 operations). [0]: https://cloud.google.com/kms https://cloud.google.com/kms