AWS cloudhsm medium security documentation change
Summary
Added guidance for user synchronization during cluster rollback and clarified key replication
Security assessment
Explicitly addresses security-critical user synchronization gaps during HSM migration rollbacks. Documents that user replication from hsm2m.medium to hsm1.medium is unsupported, requiring manual recreation to prevent access issues. This directly impacts cryptographic key access control.
Diff
diff --git a/cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md b/cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md index f51f7b801..c155b5b1c 100644 --- a//cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md +++ b//cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md @@ -263 +263,3 @@ After your cluster returns to the `ACTIVE` state, limited-write mode is lifted. -To resolve this, use the CloudHSM CLI's [key replicate](./cloudhsm_cli-key-replicate.html) command to replicate a key between two clusters. If you haven't installed it, see the instructions in [Getting started with AWS CloudHSM Command Line Interface (CLI)](./cloudhsm_cli-getting-started.html). +To address user synchronization, use [user management](./manage-hsm-users-chsm-cli.html) with CloudHSM CLI to recreate the missing users on your rolled back cluster. The users must be manually recreated because the `user replicate` command does not support syncing users from hsm2m.medium to hsm1.medium. See user replicate [known issues](./troubleshoot-sdk5-user-replicate-failures.html#troubleshoot-sdk5-user-replicate-failures-hsm2m-to-hsm1). + +To address key synchronization, use the [key replicate](./cloudhsm_cli-key-replicate.html) command to replicate a key between two clusters. If you haven't installed CloudHSM CLI, see the instructions in [Getting started with AWS CloudHSM Command Line Interface (CLI)](./cloudhsm_cli-getting-started.html).