AWS cloudhsm medium security documentation change
Summary
Removed references to known migration issues and prerequisites (token key/SDK usage requirements)
Security assessment
Removed prerequisites included security controls (token key lifecycle management and SDK connectivity requirements). Their removal could weaken migration security posture without justification.
Diff
diff --git a/cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md b/cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md index 89395e807..43f264320 100644 --- a/cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md +++ b/cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md @@ -44,2 +43,0 @@ Your existing AWS CloudHSM cluster must meet these requirements to migrate to hs -For a list of known migration issues, see [Known issues for AWS CloudHSM cluster modification](./ki-cluster-modification.html) - @@ -54,4 +51,0 @@ For a list of known migration issues, see [Known issues for AWS CloudHSM cluster - * There have been no token key creations or deletions in the past 7 days. - - * You must have used an SDK to connect with at least one HSM in the cluster in the past 7 days. -