Dedicated Key Management with AWS CloudHSM - FIPS 140-2 Level 3 Compliant Encryption
Achieve FIPS 140-2 Level 3 compliant key management with dedicated HSM instances. Learn when to choose CloudHSM over KMS and how to integrate both through KMS custom key stores.
Overview of CloudHSM
CloudHSM is a service that manages encryption keys using dedicated hardware security modules (HSMs). While KMS uses multi-tenant shared HSMs, CloudHSM provides dedicated HSM instances. It holds FIPS 140-2 Level 3 certification, meeting compliance requirements for financial, healthcare, and government organizations.
Choosing Between KMS and CloudHSM
KMS is suitable for the majority of use cases, with low operational overhead and extensive integration with AWS services. CloudHSM is the right choice when FIPS 140-2 Level 3 is mandatory, when keys must be managed on dedicated HSMs, or when PKCS#11 or JCE interfaces are required. KMS custom key stores combine the advantages of both, maintaining the KMS API and its integrations while storing keys in CloudHSM.
Cluster Design and High Availability
A CloudHSM cluster places HSM instances across multiple Availability Zones with automatic key synchronization for high availability. A configuration with HSMs in at least two AZs is recommended; if one HSM fails, processing continues on the HSM in the other AZ. The client SDK distributes requests across HSMs in the cluster using round-robin and automatically fails over on failure. HSM backups are automatically encrypted and stored in S3, used for cluster restoration and cross-region copying. Standard interfaces including PKCS#11, JCE, and OpenSSL allow applications to perform cryptographic operations, minimizing changes to existing application code. For a comprehensive study of encryption key management best practices, refer to technical books on Amazon.
CloudHSM Pricing
CloudHSM is billed hourly per HSM instance, at approximately $1.60/hour (about $1,152/month) per instance. A high-availability configuration across two AZs costs approximately $2,304/month. Compared to KMS ($1/month per key), this is significantly more expensive, so CloudHSM should be used only when FIPS 140-2 Level 3 or dedicated HSM requirements apply. Using CloudHSM as the backend through a KMS custom key store lets you operate CloudHSM keys via the KMS API, maintaining existing KMS integrations while meeting compliance requirements.
Summary
CloudHSM manages encryption keys on dedicated hardware security modules, meeting the strict compliance requirements of FIPS 140-2 Level 3. KMS custom key stores let you operate CloudHSM keys through the KMS API, and standard interfaces like PKCS#11 and JCE make integration with existing applications straightforward.