Application programming interface to generate data key pairs
A computer-implemented method for providing cryptographic services, including providing key pairs. A key management service receives a web service application programming interface or other such request to generate a key pair. To respond to the request, the key management service obtains a pregenerated key pair that is securely stored and provides the key pair in response to the request.
1. A computer-implemented method, comprising:
obtaining, at a web server providing an interface of a key management service, a web service application programming interface request to generate a data key pair;
obtaining an encrypted client managed key specified by a parameter of the request;
at a hardware security module (HSM) of the key management service:
decrypting the encrypted client managed key;
selecting a queue from a plurality of queues of different types of key pairs according to a type of data key pair specified in the request;
removing a pregenerated data key pair from the selected queue, the pregenerated data key pair comprising a public key and a private key;
providing the pregenerated data key pair to be included with a response to the request; and
encrypting the pregenerated data key pair using the decrypted client managed key, resulting in an encrypted data key pair; and
transmitting, from the web server, the response including the encrypted data key pair.
2. The computer-implemented method of claim 1 , wherein the encrypted client managed key is obtained as a result of being specified by a parameter of the request.
3. The computer-implemented method of claim 2 , wherein the parameter indicates the encrypted client managed key is to be obtained from a client storage location outside of the key management service.
4. The computer-implemented method of claim 1 , wherein selecting the queue is based at least in part on the request specifying the type of data key pair.
5. The computer-implemented method of claim 1 , wherein the plurality of queues comprises a first queue corresponding to a first cryptographic algorithm and a second queue corresponding to a second cryptographic algorithm, the first cryptographic algorithm different from the second cryptographic algorithm.
6. The computer-implemented method of claim 1 , further comprising:
detecting, as a result of transmitting the response, the HSM is idle;
determining an availability of key pairs in the selected queue is below a threshold;
generating an additional key pair of the type consistent with the selected queue; and
adding the additional key pair to the selected queue.
7. The computer-implemented method of claim 6 , wherein the threshold is determined based on a usage pattern of requests received by the HSM within a time interval.
8. The computer-implemented method of claim 1 , further comprising generating a quantity of additional key pairs based on a notification from a client indicating a schedule of future requests.
9. A system, comprising:
one or more processors; and
memory that stores computer-executable instructions that are executable by the one or more processors to cause the system to:
obtain a request to generate a data key pair; and
fulfill the request by at least:
obtaining, by commanding a hardware security module (HSM) to provide one of a plurality of pregenerated data key pairs internally stored by the HSM, a pregenerated data key pair;
performing an operation to prevent the pregenerated data key pair from being provided in response to another request; and
providing the pregenerated data key pair.
10. The system of claim 9 , wherein the instructions further cause the system to:
obtain an encrypted client managed key specified by the request;
by the HSM:
decrypt the encrypted client managed key; and
encrypt the pregenerated data key pair using the decrypted client managed key, resulting in an encrypted data key pair; and
provide the pregenerated data key pair by transmitting a response to the request, the response including the encrypted data key pair.
11. The system of claim 10 , wherein the encrypted client managed key is obtained from a client storage location outside of the HSM.
12. The system of claim 10 , wherein the instructions further cause the system to:
select a queue from a plurality of queues of different types of key pairs according to a type of data key pair indicated in the request; and
perform the operation by removing the pregenerated data key pair from the selected queue.
13. The system of claim 12 , wherein the instructions further cause the system to select the queue based at least in part on information in the request specifying the type of data key pair.
14. The system of claim 9 , wherein the instructions that cause the system to:
detect, as a result of providing the pregenerated data key pair, the HSM is idle;
determine a shortage of pregenerated key pairs; and
as a result of the HSM being idle, generate, by the HSM, one or more additional key pairs sufficient to resolve the shortage.
15. A non-transitory computer-readable storage medium storing thereon executable instructions that, as a result of being executed by one or more processors of a computer system, cause a first computer system to at least:
perform a set of operations to remove a pregenerated data key pair from a plurality of pregenerated data key pairs, the pregenerated data key pair comprising a public key and a private key;
generate a response to a request to generate a data key pair that comprises the removed pregenerated data key pair, at least by:
obtaining an encrypted client managed key;
decrypting the encrypted client managed key;
selecting a queue of a plurality of queues of different types of key pairs;
removing the pregenerated data key pair from the selected queue; and
encrypting the pregenerated data key pair using the decrypted client managed key, resulting in an encrypted data key pair; and
transmit the response to the request, the response including the encrypted data key pair.
16. The non-transitory computer-readable storage medium of claim 15 , wherein the encrypted client managed key is obtained from a storage location outside of the computer system.
17. The non-transitory computer-readable storage medium of claim 15 , wherein the queue is selected based at least in part on the request specifying the type of data key pair.
18. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions further cause the computer system to:
determine a shortage of key pairs in the selected queue;
generate one or more additional key pairs of the type consistent with the selected queue to resolve the determined shortage; and
add the one or more additional key pairs to the selected queue.
19. The non-transitory computer-readable storage medium of claim 18 , wherein the instructions further cause the computer system to detect an idle state, and wherein the shortage is determined as a result of detecting the idle state.
20. The non-transitory computer-readable storage medium of claim 18 , wherein the shortage is determined based on a prediction of future requests to be received by the computer system within a time interval, the prediction based on past usage of the computer system.