AWS AmazonElastiCache: ElastiCache serverless cutover: force-complete warning and post-migration cleanup
Summary
Adds a warning that force-completing a migration before data sync starts leaves the target with no data (and to move traffic back to the source before abandoning a migration), plus post-cutover guidance to verify data arrived and to remove migration-only resources: the inbound rule on the source security group, test clients, and the secret and customer managed key if unused elsewhere.
Security assessment
The added text is operational guidance, not a fix for a specific vulnerability. It does have security-adjacent value: it instructs users to tear down migration-only access paths and credentials (inbound security group rule on the source, test client, secret, and CMK), which reduces lingering exposure and unused secrets/keys. The force-complete warning addresses data loss/availability rather than a security weakness, so severity is medium.
Evidence
Before you decommission your source, confirm that your data arrived on your target. Compare the `CurrItems` metric of your target with the number of keys on your source, and read a few keys that your application wrote during the migration. After the migration completes, remove what you set up only for the migration: the inbound rule on your source security group, any test client you started, and the secret and the customer managed key if nothing else uses them.
Diff
diff --git a/AmazonElastiCache/latest/dg/migration-to-serverless-cutover.md b/AmazonElastiCache/latest/dg/migration-to-serverless-cutover.md index 337323d..b32c961 100644 --- a//AmazonElastiCache/latest/dg/migration-to-serverless-cutover.md +++ b//AmazonElastiCache/latest/dg/migration-to-serverless-cutover.md @@ -150,0 +151,2 @@ Use force complete in two cases: +If you force complete before the data sync starts, your target has no data. To abandon a migration, first move your application traffic back to your source, and then force complete. + @@ -170,0 +173,2 @@ Your migration endpoint now serves from your ElastiCache Serverless cache, and y +Before you decommission your source, confirm that your data arrived on your target. Compare the `CurrItems` metric of your target with the number of keys on your source, and read a few keys that your application wrote during the migration. After the migration completes, remove what you set up only for the migration: the inbound rule on your source security group, any test client you started, and the secret and the customer managed key if nothing else uses them. +