Sign
Creates a digital
signature
Digital signatures are generated and verified by using asymmetric key pair, such as an RSA or ECC pair that is represented by an asymmetric KMS key. The key owner (or an authorized user) uses their private key to sign a message. Anyone with the public key can verify that the message was signed with that particular private key and that the message hasn't changed since it was signed.
To use the Sign
operation, provide the following information:
-
Use the
KeyId
parameter to identify an asymmetric KMS key with aKeyUsage
value ofSIGN_VERIFY
. To get theKeyUsage
value of a KMS key, use the DescribeKey operation. The caller must havekms:Sign
permission on the KMS key. -
Use the
Message
parameter to specify the message or message digest to sign. You can submit messages of up to 4096 bytes. To sign a larger message, generate a hash digest of the message, and then provide the hash digest in theMessage
parameter. To indicate whether the message is a full message or a digest, use theMessageType
parameter. -
Choose a signing algorithm that is compatible with the KMS key.
Important
When signing a message, be sure to record the KMS key and the signing algorithm. This information is required to verify the signature.
Note
Best practices recommend that you limit the time during which any signature is effective. This deters an attack where the actor uses a signed message to establish validity repeatedly or long after the message is superseded. Signatures do not include a timestamp, but you can include a timestamp in the signed message to help you detect when its time to refresh the signature.
To verify the signature that this operation generates, use the Verify operation. Or use the GetPublicKey operation to download the public key and then use the public key to verify the signature outside of Amazon KMS.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of Amazon KMS keys in the Amazon Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify
the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:Sign (key policy)
Related operations: Verify
Eventual consistency: The Amazon KMS API follows an eventual consistency model. For more information, see Amazon KMS eventual consistency.
Request Syntax
{
"DryRun": boolean
,
"GrantTokens": [ "string
" ],
"KeyId": "string
",
"Message": blob
,
"MessageType": "string
",
"SigningAlgorithm": "string
"
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
Note
In the following list, the required parameters are described first.
- KeyId
-
Identifies an asymmetric KMS key. Amazon KMS uses the private key in the asymmetric KMS key to sign the message. The
KeyUsage
type of the KMS key must beSIGN_VERIFY
. To find theKeyUsage
of a KMS key, use the DescribeKey operation.To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with
"alias/"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.For example:
-
Key ID:
1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN:
arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name:
alias/ExampleAlias
-
Alias ARN:
arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 2048.
Required: Yes
-
- Message
-
Specifies the message or message digest to sign. Messages can be 0-4096 bytes. To sign a larger message, provide a message digest.
If you provide a message digest, use the
DIGEST
value ofMessageType
to prevent the digest from being hashed again while signing.Type: Base64-encoded binary data object
Length Constraints: Minimum length of 1. Maximum length of 4096.
Required: Yes
- SigningAlgorithm
-
Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.
Type: String
Valid Values:
RSASSA_PSS_SHA_256 | RSASSA_PSS_SHA_384 | RSASSA_PSS_SHA_512 | RSASSA_PKCS1_V1_5_SHA_256 | RSASSA_PKCS1_V1_5_SHA_384 | RSASSA_PKCS1_V1_5_SHA_512 | ECDSA_SHA_256 | ECDSA_SHA_384 | ECDSA_SHA_512 | SM2DSA
Required: Yes
- DryRun
-
Checks if your request will succeed.
DryRun
is an optional parameter.To learn more about how to use this parameter, see Testing your permissions in the Amazon Key Management Service Developer Guide.
Type: Boolean
Required: No
- GrantTokens
-
A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Amazon Key Management Service Developer Guide.
Type: Array of strings
Array Members: Minimum number of 0 items. Maximum number of 10 items.
Length Constraints: Minimum length of 1. Maximum length of 8192.
Required: No
- MessageType
-
Tells Amazon KMS whether the value of the
Message
parameter should be hashed as part of the signing algorithm. UseRAW
for unhashed messages; useDIGEST
for message digests, which are already hashed.When the value of
MessageType
isRAW
, Amazon KMS uses the standard signing algorithm, which begins with a hash function. When the value isDIGEST
, Amazon KMS skips the hashing step in the signing algorithm.Important
Use the
DIGEST
value only when the value of theMessage
parameter is a message digest. If you use theDIGEST
value with an unhashed message, the security of the signing operation can be compromised.When the value of
MessageType
isDIGEST
, the length of theMessage
value must match the length of hashed messages for the specified signing algorithm.You can submit a message digest and omit the
MessageType
or specifyRAW
so the digest is hashed again while signing. However, this can cause verification failures when verifying with a system that assumes a single hash.The hashing algorithm in that
Sign
uses is based on theSigningAlgorithm
value.-
Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
-
Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
-
Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
-
SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
Type: String
Valid Values:
RAW | DIGEST
Required: No
-
Response Syntax
{
"KeyId": "string",
"Signature": blob,
"SigningAlgorithm": "string"
}
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.
- KeyId
-
The Amazon Resource Name (key ARN) of the asymmetric KMS key that was used to sign the message.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 2048.
- Signature
-
The cryptographic signature that was generated for the message.
-
When used with the supported RSA signing algorithms, the encoding of this value is defined by PKCS #1 in RFC 8017
. -
When used with the
ECDSA_SHA_256
,ECDSA_SHA_384
, orECDSA_SHA_512
signing algorithms, this value is a DER-encoded object as defined by ANSI X9.62–2005 and RFC 3279 Section 2.2.3. This is the most commonly used signature format and is appropriate for most uses.
When you use the HTTP API or the Amazon CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
Type: Base64-encoded binary data object
Length Constraints: Minimum length of 1. Maximum length of 6144.
-
- SigningAlgorithm
-
The signing algorithm that was used to sign the message.
Type: String
Valid Values:
RSASSA_PSS_SHA_256 | RSASSA_PSS_SHA_384 | RSASSA_PSS_SHA_512 | RSASSA_PKCS1_V1_5_SHA_256 | RSASSA_PKCS1_V1_5_SHA_384 | RSASSA_PKCS1_V1_5_SHA_512 | ECDSA_SHA_256 | ECDSA_SHA_384 | ECDSA_SHA_512 | SM2DSA
Errors
For information about the errors that are common to all actions, see Common Errors.
- DependencyTimeoutException
-
The system timed out while trying to fulfill the request. You can retry the request.
HTTP Status Code: 500
- DisabledException
-
The request was rejected because the specified KMS key is not enabled.
HTTP Status Code: 400
- DryRunOperationException
-
The request was rejected because the DryRun parameter was specified.
HTTP Status Code: 400
- InvalidGrantTokenException
-
The request was rejected because the specified grant token is not valid.
HTTP Status Code: 400
- InvalidKeyUsageException
-
The request was rejected for one of the following reasons:
-
The
KeyUsage
value of the KMS key is incompatible with the API operation. -
The encryption algorithm or signing algorithm specified for the operation is incompatible with the type of key material in the KMS key
(KeySpec
).
For encrypting, decrypting, re-encrypting, and generating data keys, the
KeyUsage
must beENCRYPT_DECRYPT
. For signing and verifying messages, theKeyUsage
must beSIGN_VERIFY
. For generating and verifying message authentication codes (MACs), theKeyUsage
must beGENERATE_VERIFY_MAC
. For deriving key agreement secrets, theKeyUsage
must beKEY_AGREEMENT
. To find theKeyUsage
of a KMS key, use the DescribeKey operation.To find the encryption or signing algorithms supported for a particular KMS key, use the DescribeKey operation.
HTTP Status Code: 400
-
- KeyUnavailableException
-
The request was rejected because the specified KMS key was not available. You can retry the request.
HTTP Status Code: 500
- KMSInternalException
-
The request was rejected because an internal exception occurred. The request can be retried.
HTTP Status Code: 500
- KMSInvalidStateException
-
The request was rejected because the state of the specified resource is not valid for this request.
This exceptions means one of the following:
-
The key state of the KMS key is not compatible with the operation.
To find the key state, use the DescribeKey operation. For more information about which key states are compatible with each Amazon KMS operation, see Key states of Amazon KMS keys in the Amazon Key Management Service Developer Guide .
-
For cryptographic operations on KMS keys in custom key stores, this exception represents a general failure with many possible causes. To identify the cause, see the error message that accompanies the exception.
HTTP Status Code: 400
-
- NotFoundException
-
The request was rejected because the specified entity or resource could not be found.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific Amazon SDKs, see the following: