By using standard signing, hashing algorithms, and key parameters, receivers can verify signatures in any environment that has access to the public key. In public-key cryptography, producing a digital signature requires the private key in a public/private key pair, whereas verifying the signature requires only the public key. About signature verification Digital signatures If you’re interested in signing JSON Web Tokens (JWTs) with AWS KMS, and then later validating those signatures in large-scale distributed applications, read on for an example use case and working code examples. In our use case, AWS KMS signs the data, but the verification is performed in independent, distributed environments. This blog post describes a delegated authorization use case, to illustrate how to approach this problem at scale. However, when you need to verify a signature in high-throughput or decoupled architectures, using the AWS KMS API might not be practical. The asymmetric CMKs offer digital signature capability, which data consumers can use to verify that data is from a trusted producer and is unaltered in transit.ĪWS KMS provides convenient API methods over asymmetric CMKs that you can use to both sign and verify signatures. The service supports both symmetric and asymmetric customer master keys (CMKs). More info.ĪWS Key Management Service (AWS KMS) makes it easy to create and manage cryptographic keys in your applications.
To prevent breaking changes, AWS KMS is keeping some variations of this term. August 31, 2021: AWS KMS is replacing the term customer master key (CMK) with AWS KMS key and KMS key.
0 kommentar(er)
