Amazon KMS condition keys for attested platforms - Amazon Key Management Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon KMS condition keys for attested platforms

Amazon KMS provides condition keys to support cryptographic attestation for Amazon Nitro Enclaves and NitroTPM. Amazon Nitro Enclaves is an Amazon EC2 capability that lets you create isolated compute environments called enclaves to protect and process highly sensitive data. NitroTPM extends similar attestation functionality to EC2 instances.

When you call the Decrypt, DeriveSharedSecret, GenerateDataKey, GenerateDataKeyPair, or GenerateRandom API operations with a signed attestation document, these APIs encrypt the plaintext in the response under the public key from the attestation document, and return ciphertext instead of plaintext. This ciphertext can be decrypted only by using the private key in the enclave. For more information, see Cryptographic attestation support in Amazon KMS.

Note

If you don't provide a key policy when you create an Amazon KMS key, Amazon creates one for you. This default key policy grants the Amazon Web Services accounts that own the KMS key full access to the key and allows the account to use IAM policies to allow access to the key. This policy allows all actions like Decrypt. Amazon recommends applying principal of Least-privilege permissions to your KMS key policies. You can also restrict access by modifying the KMS key policy action for kms:* to NotAction:kms:Decrypt.

The following condition keys let you limit the permissions for these operations based on the contents of the signed attestation document. Before allowing an operation, Amazon KMS compares the attestation document to the values in these Amazon KMS condition keys.