Infrastructure security in Amazon Key Management Service - 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.

Infrastructure security in Amazon Key Management Service

As a managed service, Amazon Key Management Service (Amazon KMS) is protected by the Amazon global network security procedures that are described in the Amazon Web Services: Overview of Security Processes.

To access Amazon KMS over the network, you can call the Amazon KMS API operations that are described in the Amazon Key Management Service API Reference. Amazon KMS supports Transport Layer Security (TLS) 1.0—1.3 in all regions, except Amazon GovCloud (US) and China Regions. The Amazon GovCloud (US) region only supports TLS 1.0—1.2 for Amazon KMS service endpoints. Amazon KMS does not support hybrid post-quantum TLS for endpoints in Amazon GovCloud (US). To use the standard Amazon KMS endpoints, clients must support TLS 1.0 or later. To use the Amazon KMS FIPS endpoints, clients must support TLS 1.2 or later. Amazon KMS recommends you always use the latest supported TLS version. Clients must also support cipher suites with perfect forward secrecy (PFS) such as Ephemeral Diffie-Hellman (DHE) or Elliptic Curve Ephemeral Diffie-Hellman (ECDHE). Most modern systems, such as Java 7 and later, support these modes.

Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the Amazon Security Token Service (Amazon STS) to generate temporary security credentials to sign requests.

You can call these API operations from any network location, but Amazon KMS supports global policy conditions that let you control access to a KMS key based on the source IP address, VPC, and VPC endpoint. You can use these condition keys in key policies and IAM policies. However, these conditions can prevent Amazon from using the KMS key on your behalf. For details, see Amazon global condition keys.

For example, the following key policy statement allows users who can assume the KMSTestRole role to use this Amazon KMS key for the specified cryptographic operations unless the source IP address is one of the IP addresses specified in the policy.

{ "Version": "2012-10-17", "Statement": { "Effect": "Allow", "Principal": {"AWS": "arn:aws:iam::111122223333:role/KMSTestRole"}, "Action": [ "kms:Encrypt", "kms:Decrypt", "kms:ReEncrypt*", "kms:GenerateDataKey*", "kms:DescribeKey" ], "Resource": "*", "Condition": { "NotIpAddress": { "aws:SourceIp": [ "", "" ] } } } }

Isolation of Physical Hosts

The security of the physical infrastructure that Amazon KMS uses is subject to the controls described in the Physical and Environmental Security section of the Amazon Web Services: Overview of Security Processes. You can find more detail in compliance reports and third-party audit findings listed in the previous section.

Amazon KMS is supported by dedicated hardened hardware security modules (HSMs) designed with specific controls to resist physical attacks. The HSMs are physical devices that do not have a virtualization layer, such as a hypervisor, that shares the physical device among several logical tenants. The key material for Amazon KMS keys is stored only in volatile memory on the HSMs, and only while the KMS key is in use. This memory is erased when the HSM moves out of the operational state, including intended and unintended shutdowns and resets. For detailed information about the operation of Amazon KMS HSMs, see Amazon Key Management Service Cryptographic Details.