dms serverless replication issue

The issue you're experiencing with your DMS serverless task not replicating data beyond March 25th is likely related to how the task was configured and the interaction between your existing ongoing replication task and the new serverless task.

To address this issue and ensure your new DMS serverless task picks up the CDC (Change Data Capture) properly, you can try the following steps:

1. First, it's important to note that stopping or deleting the ongoing changes task may not automatically cause the serverless task to pick up the changes. The serverless task is likely using a specific point in time or system change number (SCN) as its starting point for replication.

2. Before making any changes, verify the current state of both tasks and check their logs for any error messages or warnings that might explain the discrepancy in data replication.

3. To fix this issue, you'll need to modify the serverless task's configuration. Stop the serverless task and update its CDC start point. You can do this by specifying a more recent timestamp or SCN that corresponds to a point after March 25th.

4. After updating the CDC start point, restart the serverless task. This should cause it to begin replicating changes from the new start point, including data changes that occurred after March 25th.

5. Monitor the serverless task closely after restarting to ensure it's now capturing and applying the more recent changes.

6. Once you've confirmed that the serverless task is successfully replicating current data, you can consider stopping and deleting the original ongoing replication task.

7. Keep in mind that there might be a brief period of data inconsistency during this transition. Ensure that your application can handle this, or consider performing this operation during a maintenance window.

8. After the transition is complete, continue to monitor the serverless task to ensure it's performing as expected and capturing all ongoing changes.

By following these steps, you should be able to get your DMS serverless task to pick up the CDC properly and continue replication from the current point in time, allowing you to eventually remove the original ongoing replication task.

Sources
Issue with AWS DMS Full Load + CDC Task Not Reflecting Newly Created Tables in Target DB | AWS re:Post
Connect DMS to SQL Sever Read-Replica for CDC Ongoing Replication | AWS re:Post