This alert monitors the read latency for a replication instance in AWS Database Migration Service (DMS). High read latency can impact the performance and timeliness of database migration tasks, potentially leading to delays in data synchronization or replication. The alert is triggered when the average read latency per replication instance exceeds 20 milliseconds over a 10-minute period. Monitoring this metric helps ensure efficient and timely migration of data, minimizing disruptions to dependent applications or services. Customization Guidance: - Threshold: Adjust the threshold based on the performance requirements of your migration workload and the acceptable latency for your use case. - Monitoring Period: Modify the monitoring period to capture patterns during high workload periods or critical migration phases. - Notification Frequency: Set notification frequency to balance between prompt response and avoiding alert fatigue, especially during large-scale migrations. Action: If this alert is triggered, consider optimizing the source or target database performance, increasing the replication instance size, or reviewing and tuning your migration task settings to reduce latency.

This alert monitors the Change Data Capture (CDC) throughput bandwidth utilization for AWS Database Migration Service (DMS). High utilization of CDC throughput bandwidth may indicate that the replication instance is nearing its performance limits, potentially leading to delays or dropped changes during data migration. The alert is triggered when the CDC throughput bandwidth utilization exceeds 500MB over a 10-minute period. Monitoring this metric helps ensure that the replication process remains efficient and reliable, avoiding bottlenecks that could disrupt migration tasks. Customization Guidance: - Threshold: Adjust the threshold based on your replication instance size and the expected data change rate in your source database. - Monitoring Period: Modify the monitoring period to reflect the variability in data changes during different times or workloads. - Notification Frequency: Set notification frequency to avoid repeated alerts during periods of sustained high throughput while still ensuring timely response. Action: If this alert is triggered, consider scaling up the replication instance, optimizing task settings, or reducing the workload by staggering large data updates to ensure the bandwidth capacity is not exceeded.

This alert monitors the rate of incoming Change Data Capture (CDC) changes for AWS Database Migration Service (DMS). A high rate of incoming CDC changes can strain the replication instance and increase latency, potentially delaying the replication process and affecting data consistency. The alert is triggered when the rate of incoming CDC changes exceeds 5 changes per second over a 10-minute period. Monitoring this metric helps ensure the replication instance can handle the incoming data change workload without performance degradation, maintaining the accuracy and timeliness of data replication. Customization Guidance: - Threshold: Adjust the threshold based on the expected change rate for your source database and the capacity of the replication instance. - Monitoring Period: Modify the monitoring period to align with times of peak database activity or during critical migration phases. - Notification Frequency: Set notification frequency to balance immediate action with avoiding excessive alerts during prolonged high activity. Action: If this alert is triggered, consider scaling up the replication instance, optimizing the source database to reduce change volume, or staggering updates to smooth out peaks in the CDC changes rate.

This alert monitors the write latency for a replication instance in AWS Database Migration Service (DMS). High write latency can slow down the replication process, leading to delays in applying changes to the target database and potential data consistency issues. The alert is triggered when the average write latency per replication instance exceeds 20 milliseconds over a 10-minute period. Monitoring this metric helps ensure timely application of changes to the target database, maintaining data synchronization and minimizing disruptions to downstream systems. Customization Guidance: - Threshold: Adjust the threshold based on the performance requirements of your target database and acceptable latency levels for your workload. - Monitoring Period: Modify the monitoring period to reflect the timeframes of peak replication activity or critical workloads. - Notification Frequency: Set notification frequency to ensure timely responses without generating excessive alerts during sustained high activity. Action: If this alert is triggered, consider optimizing the target database performance, increasing the replication instance size, or reviewing and tuning your migration task settings to reduce write latency.

This alert monitors swap usage for a replication instance in AWS Database Migration Service (DMS). High swap usage indicates that the instance is using disk space for memory operations, which can significantly degrade performance and slow down the replication process. The alert is triggered when the swap usage exceeds 1 Gigabytes of swap memory for a replication instance over a 10-minute period. Monitoring this metric helps ensure the replication instance operates efficiently, minimizing performance bottlenecks that could disrupt migration tasks. Customization Guidance: - Threshold: Adjust the threshold based on the instance's memory capacity and workload characteristics. - Monitoring Period: Modify the monitoring period to align with expected memory-intensive periods or critical migration phases. - Notification Frequency: Set notification frequency to avoid alert fatigue while ensuring timely action during critical events. Action: If this alert is triggered, consider increasing the replication instance size, optimizing migration task settings, or reducing concurrent workloads to decrease memory pressure and swap usage.