AWS AmazonElastiCache: Clarify migration completion, billing, and security cleanup
Summary
Adds a billing note for StopMigration versus CompleteMigration, clarifies force-complete behavior for ready-to-sync migrations, and restructures verification and cleanup steps including removing the source security group inbound rule and migration secret/CMK.
Security assessment
The cleanup guidance documents removing temporary inbound network access and migration credentials/keys, which is security hardening best practice, but the diff does not reference a specific vulnerability or incident.
Evidence
+ 1. Remove the inbound rule on your source security group.
Diff
diff --git a/AmazonElastiCache/latest/dg/migration-to-serverless-cutover.md b/AmazonElastiCache/latest/dg/migration-to-serverless-cutover.md index ddc996d..353a52d 100644 --- a//AmazonElastiCache/latest/dg/migration-to-serverless-cutover.md +++ b//AmazonElastiCache/latest/dg/migration-to-serverless-cutover.md @@ -105,0 +106,4 @@ ElastiCache stops replicating and your application continues to be served by you +###### Important + +Billing does not stop when you stop the data sync. `StopMigration` leaves the migration infrastructure provisioned. `CompleteMigration` is the call that ends the migration and its charges. + @@ -151 +155 @@ 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. +While the migration is `ready-to-sync`, `CompleteMigration` requires force. 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. @@ -173 +177,29 @@ 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. Wait a few minutes after the completion event before you compare. Right after completion, `CurrItems` and `DBSIZE` can briefly read higher than the final count. Your target can hold more keys than your source, because after cutover your application writes only to your target. 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. +Before you decommission your source, confirm that your data arrived on your target. + +###### To verify your data + + 1. Wait a few minutes after the completion event before you compare. Right after completion, `CurrItems` and `DBSIZE` can briefly read higher than the final count. + + 2. Compare the `CurrItems` metric of your target with the number of keys on your source. + + 3. Read a few keys that your application wrote during the migration. + + + + +###### Note + +Your target can hold more keys than your source, because after cutover your application writes only to your target. + +After the migration completes, remove what you set up only for the migration: + +###### To clean up + + 1. Remove the inbound rule on your source security group. + + 2. Remove any test client you started. + + 3. Remove the secret and the customer managed key if nothing else uses them. + + +