AWS dms documentation change

Service: dms · 2025-06-13 · Documentation low

File: dms/latest/userguide/CHAP_ReplicationInstance.Modifying.md

Summary

Added best practices section for modifying replication instances including pre/post-modification steps and timing recommendations

Security assessment

The changes focus on operational best practices and workflow management without addressing security vulnerabilities or security features

Diff

diff --git a/dms/latest/userguide/CHAP_ReplicationInstance.Modifying.md b/dms/latest/userguide/CHAP_ReplicationInstance.Modifying.md
index 902c9d097..589485e1f 100644
--- a//dms/latest/userguide/CHAP_ReplicationInstance.Modifying.md
+++ b//dms/latest/userguide/CHAP_ReplicationInstance.Modifying.md
@@ -4,0 +5,2 @@
+Best practices when modifying a replication instance
+
@@ -46,0 +49,46 @@ In most cases, the default allocation of storage is sufficient. However, it's al
+## Best practices when modifying a replication instance
+
+When modifying a replication instance, following these best practices helps ensure a successful update with minimal impact to your migration workflows. Take the following key steps before, during, and after modifications to maintain data integrity and operational efficiency throughout the process.
+
+**Plan modification timing:**
+    
+
+  * You can either apply changes immediately or schedule them for the next maintenance window.
+
+  * Schedule during low-traffic periods to minimize impact.
+
+
+
+
+**Pre-modification steps:**
+    
+
+  * Stop all active replication tasks.
+
+  * Verify all tasks have successfully stopped.
+
+  * Document current configuration task settings.
+
+
+
+
+**During modification:**
+    
+
+  * Monitor the modification progress.
+
+  * Wait for "Available" status before proceeding.
+
+
+
+
+**Post-modification steps:**
+    
+
+  * Resume all previously stopped tasks.
+
+  * Confirm tasks are running correctly.
+
+
+
+