AWS cloudhsm documentation change
Summary
Added automatic migration date note and updated migration process description
Security assessment
Changes relate to migration scheduling and process clarity. No security vulnerabilities addressed or new security features documented.
Diff
diff --git a/cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md b/cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md index c155b5b1c..c581c34d0 100644 --- a//cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md +++ b//cloudhsm/latest/userguide/hsm1-to-hsm2-migration.md @@ -12,0 +13,4 @@ Before starting the migration, make sure your application follows the recommenda +###### Note + +Automatic migrations to hsm2m.medium will begin on January 20th, 2026. + @@ -15 +19 @@ Before starting the migration, make sure your application follows the recommenda -You can start the migration using the AWS CloudHSM Console, the AWS CLI, or the AWS CloudHSM API. No matter where you initiate it, the AWS CloudHSM cluster migration uses the `modify-cluster` API endpoint. Once the migration starts, your entire cluster enters a limited-write mode. For more information, see Cluster limited-write mode. +You can start the migration using the AWS CloudHSM Console, the AWS CLI, or the AWS CloudHSM API. No matter where you initiate it, the AWS CloudHSM cluster migration uses the `modify-cluster` API endpoint. Alternatively, AWS CloudHSM will automatically migrate cluster on your behalf. Once the migration starts, your entire cluster enters a limited-write mode. For more information, see Cluster limited-write mode. @@ -67 +71 @@ The previous restriction which prevented customers with token key workloads from -When you start the cluster migration, it enters a limited-write mode. Operations that can change the HSM state are rejected. All read operations remain unaffected. +When your cluster starts migration, it enters a limited-write mode. Operations that can change the HSM state are rejected. All read operations remain unaffected.