ImportKey
Imports symmetric keys and public key certificates in PEM format (base64 encoded) into AWS Payment Cryptography.
AWS Payment Cryptography simplifies key exchange by replacing the existing paper-based approach with a modern electronic approach. With ImportKey
you can import symmetric keys using either symmetric and asymmetric key exchange mechanisms.
For symmetric key exchange, AWS Payment Cryptography uses the ANSI X9 TR-31 norm in accordance with PCI PIN guidelines. And for asymmetric key exchange, AWS Payment Cryptography supports ANSI X9 TR-34 norm and RSA wrap and unwrap key exchange mechanisms. Asymmetric key exchange methods are typically used to establish bi-directional trust between the two parties exhanging keys and are used for initial key exchange such as Key Encryption Key (KEK) or Zone Master Key (ZMK). After which you can import working keys using symmetric method to perform various cryptographic operations within AWS Payment Cryptography.
The TR-34 norm is intended for exchanging 3DES keys only and keys are imported in a WrappedKeyBlock format. Key attributes (such as KeyUsage, KeyAlgorithm, KeyModesOfUse, Exportability) are contained within the key block. With RSA wrap and unwrap, you can exchange both 3DES and AES-128 keys. The keys are imported in a WrappedKeyCryptogram format and you will need to specify the key attributes during import.
You can also import a root public key certificate, used to sign other public key certificates, or a trusted public key certificate under an already established root public key certificate.
To import a public root key certificate
You can also import a root public key certificate, used to sign other public key certificates, or a trusted public key certificate under an already established root public key certificate.
To import a public root key certificate
Using this operation, you can import the public component (in PEM cerificate format) of your private root key. You can use the imported public root key certificate for digital signatures, for example signing wrapping key or signing key in TR-34, within your AWS Payment Cryptography account.
Set the following parameters:
-
KeyMaterial
:RootCertificatePublicKey
-
KeyClass
:PUBLIC_KEY
-
KeyModesOfUse
:Verify
-
KeyUsage
:TR31_S0_ASYMMETRIC_KEY_FOR_DIGITAL_SIGNATURE
-
PublicKeyCertificate
: The public key certificate in PEM format (base64 encoded) of the private root key under import.
To import a trusted public key certificate
The root public key certificate must be in place and operational before you import a trusted public key certificate. Set the following parameters:
-
KeyMaterial
:TrustedCertificatePublicKey
-
CertificateAuthorityPublicKeyIdentifier
:KeyArn
of theRootCertificatePublicKey
. -
KeyModesOfUse
andKeyUsage
: Corresponding to the cryptographic operations such as wrap, sign, or encrypt that you will allow the trusted public key certificate to perform. -
PublicKeyCertificate
: The trusted public key certificate in PEM format (base64 encoded) under import.
To import initial keys (KEK or ZMK or similar) using TR-34
Using this operation, you can import initial key using TR-34 asymmetric key exchange. In TR-34 terminology, the sending party of the key is called Key Distribution Host (KDH) and the receiving party of the key is called Key Receiving Device (KRD). During the key import process, KDH is the user who initiates the key import and KRD is AWS Payment Cryptography who receives the key.
To initiate TR-34 key import, the KDH must obtain an import token by calling GetParametersForImport. This operation generates an encryption keypair for the purpose of key import, signs the key and returns back the wrapping key certificate (also known as KRD wrapping certificate) and the root certificate chain. The KDH must trust and install the KRD wrapping certificate on its HSM and use it to encrypt (wrap) the KDH key during TR-34 WrappedKeyBlock generation. The import token and associated KRD wrapping certificate expires after 7 days.
Next the KDH generates a key pair for the purpose of signing the encrypted KDH key and provides the public certificate of the signing key to AWS Payment Cryptography. The KDH will also need to import the root certificate chain of the KDH signing certificate by calling ImportKey
for RootCertificatePublicKey
. For more information on TR-34 key import, see section Importing symmetric keys in the
AWS Payment Cryptography User Guide.
Set the following parameters:
-
KeyMaterial
: UseTr34KeyBlock
parameters. -
CertificateAuthorityPublicKeyIdentifier
: TheKeyARN
of the certificate chain that signed the KDH signing key certificate. -
ImportToken
: Obtained from KRD by calling GetParametersForImport. -
WrappedKeyBlock
: The TR-34 wrapped key material from KDH. It contains the KDH key under import, wrapped with KRD wrapping certificate and signed by KDH signing private key. This TR-34 key block is typically generated by the KDH Hardware Security Module (HSM) outside of AWS Payment Cryptography. -
SigningKeyCertificate
: The public key certificate in PEM format (base64 encoded) of the KDH signing key generated under the root certificate (CertificateAuthorityPublicKeyIdentifier) imported in AWS Payment Cryptography.
To import initial keys (KEK or ZMK or similar) using RSA Wrap and Unwrap
Using this operation, you can import initial key using asymmetric RSA wrap and unwrap key exchange method. To initiate import, call GetParametersForImport with KeyMaterial
set to KEY_CRYPTOGRAM
to generate an import token. This operation also generates an encryption keypair for the purpose of key import, signs the key and returns back the wrapping key certificate in PEM format (base64 encoded) and its root certificate chain. The import token and associated KRD wrapping certificate expires after 7 days.
You must trust and install the wrapping certificate and its certificate chain on the sending HSM and use it to wrap the key under export for WrappedKeyCryptogram generation. Next call ImportKey
with KeyMaterial
set to KEY_CRYPTOGRAM
and provide the ImportToken
and KeyAttributes
for the key under import.
To import working keys using TR-31
AWS Payment Cryptography uses TR-31 symmetric key exchange norm to import working keys. A KEK must be established within AWS Payment Cryptography by using TR-34 key import or by using CreateKey. To initiate a TR-31 key import, set the following parameters:
-
KeyMaterial
: UseTr31KeyBlock
parameters. -
WrappedKeyBlock
: The TR-31 wrapped key material. It contains the key under import, encrypted using KEK. The TR-31 key block is typically generated by a HSM outside of AWS Payment Cryptography. -
WrappingKeyIdentifier
: TheKeyArn
of the KEK that AWS Payment Cryptography uses to decrypt or unwrap the key under import.
Cross-account use: This operation can't be used across different AWS accounts.
Related operations:
Request Syntax
{
"Enabled": boolean
,
"KeyCheckValueAlgorithm": "string
",
"KeyMaterial": { ... },
"Tags": [
{
"Key": "string
",
"Value": "string
"
}
]
}
Request Parameters
The request accepts the following data in JSON format.
- Enabled
-
Specifies whether import key is enabled.
Type: Boolean
Required: No
- KeyCheckValueAlgorithm
-
The algorithm that AWS Payment Cryptography uses to calculate the key check value (KCV). It is used to validate the key integrity.
For TDES keys, the KCV is computed by encrypting 8 bytes, each with value of zero, with the key to be checked and retaining the 3 highest order bytes of the encrypted result. For AES keys, the KCV is computed using a CMAC algorithm where the input data is 16 bytes of zero and retaining the 3 highest order bytes of the encrypted result.
Type: String
Valid Values:
CMAC | ANSI_X9_24
Required: No
- KeyMaterial
-
The key or public key certificate type to use during key material import, for example TR-34 or RootCertificatePublicKey.
Type: ImportKeyMaterial object
Note: This object is a Union. Only one member of this object can be specified or returned.
Required: Yes
- Tags
-
Assigns one or more tags to the AWS Payment Cryptography key. Use this parameter to tag a key when it is imported. To tag an existing AWS Payment Cryptography key, use the TagResource operation.
Each tag consists of a tag key and a tag value. Both the tag key and the tag value are required, but the tag value can be an empty (null) string. You can't have more than one tag on an AWS Payment Cryptography key with the same tag key. If you specify an existing tag key with a different tag value, AWS Payment Cryptography replaces the current tag value with the specified one.
Important
Don't include personal, confidential or sensitive information in this field. This field may be displayed in plaintext in AWS CloudTrail logs and other output.
Note
Tagging or untagging an AWS Payment Cryptography key can allow or deny permission to the key.
Type: Array of Tag objects
Array Members: Minimum number of 0 items. Maximum number of 200 items.
Required: No
Response Syntax
{
"Key": {
"CreateTimestamp": number,
"DeletePendingTimestamp": number,
"DeleteTimestamp": number,
"Enabled": boolean,
"Exportable": boolean,
"KeyArn": "string",
"KeyAttributes": {
"KeyAlgorithm": "string",
"KeyClass": "string",
"KeyModesOfUse": {
"Decrypt": boolean,
"DeriveKey": boolean,
"Encrypt": boolean,
"Generate": boolean,
"NoRestrictions": boolean,
"Sign": boolean,
"Unwrap": boolean,
"Verify": boolean,
"Wrap": boolean
},
"KeyUsage": "string"
},
"KeyCheckValue": "string",
"KeyCheckValueAlgorithm": "string",
"KeyOrigin": "string",
"KeyState": "string",
"UsageStartTimestamp": number,
"UsageStopTimestamp": number
}
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
Errors
- AccessDeniedException
-
You do not have sufficient access to perform this action.
HTTP Status Code: 400
- ConflictException
-
This request can cause an inconsistent state for the resource.
HTTP Status Code: 400
- InternalServerException
-
The request processing has failed because of an unknown error, exception, or failure.
HTTP Status Code: 500
- ResourceNotFoundException
-
The request was denied due to an invalid resource error.
HTTP Status Code: 400
- ServiceQuotaExceededException
-
This request would cause a service quota to be exceeded.
HTTP Status Code: 400
- ServiceUnavailableException
-
The service cannot complete the request.
HTTP Status Code: 500
- ThrottlingException
-
The request was denied due to request throttling.
HTTP Status Code: 400
- ValidationException
-
The request was denied due to an invalid request error.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: