AWS Key Management Service HSM
AWS Key Management Service HSM, from Amazon Web Services, Inc., holds FIPS 140-2 certificate #4523 at overall level 3. The validation is active, with a sunset date of 2026-09-21. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.
Caveat: When installed, initialized and configured as specified in Section 3 of the Security Policy
Certificate
| Certificate number | 4523 |
|---|---|
| Standard | FIPS 140-2 |
| Status | active |
| Sunset date | 2026-09-21 |
| Overall level | 3 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Amazon Web Services, Inc. · website |
| Hardware versions | 3.0 |
| Firmware versions | 1.7.100, 1.7.102 and 1.7.103 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Amazon AWS Key Management Service HSM is a multi-chip standalone hardware cryptographic appliance designed to provide dedicated cryptographic functions to meet the security and scalability requirements of the AWS Key Management Service (KMS). The cryptographic boundary is defined as the secure chassis of the appliance. All key materials are maintained exclusively in volatile memory in the appliance and are erased immediately upon detection of physical tampering.
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (14)
| Algorithm | CAVP certificates |
|---|---|
| AES | A1791, A1908 |
| CKG | vendor affirmed |
| CVL | A1908 |
| DRBG | A1791, A1908 |
| ECDSA | A1908 |
| ENT | |
| HMAC | A1908 |
| KAS | A1908 |
| KBKDF | A1910 |
| KDA | A1908 |
| KTS | |
| KTS-RSA | |
| RSA | A1908 |
| SHS | A1908 |
Allowed algorithms
RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength)
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2023-05-19 | Initial | Acumen Security |
Status timeline
As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.
- 2026-08-21: first observed by this tracker, status active
- Validation dates on record: 2023-05-19