Known issues for hsm2m.medium instances
The following issues impact all hsm2m.medium instances.
Topics
Issue: Login latency increases due to increased PBKDF2 iterations
-
Impact: For increased security, hsm2m.medium performs 60,000 iterations of Password-Based Key Derivation Function 2 (PBKDF2) during login requests compared to 1,000 in hsm1.medium. This increase may result in an increased latency of up to 2 seconds (2s) per login request.
The default timeout for the AWS CloudHSM Client SDKs is 20s. Login requests may timeout and result in an error.
-
Workaround: If possible, serialize login requests in the same application to avoid extended latency during login.
-
Resolution status: Future versions of the Client SDK will have an increased default timeout for login requests to account for this increased latency.
Issue: A CO using trying to set the trusted attribute of a key will fail with Client SDK 5.12.0 and earlier
Impact: Any CO user attempting to set the trusted attribute of a key will receive an error indicating that
User type should be CO or CU
.-
Resolution: Future versions of the Client SDK will resolve this issue. Updates will be annoynced in our user guide's Document history.