Issues with ongoing loads/replication/delta loads using DMS

Need your help as this falls outside my expertise, here is my customer question:

Currently we are using AWS Database Migration service (DMS) to do one time loads and ongoing loads into red-shift from different Sources.

DMS is great when we doing One time loads. However there are some issues with ongoing loads/ replication/ delta loads.

Sometimes counts are not matching with the error messages log sequence file is missing, even though that particular log file exists on the server.

Solution from support is restart the task. Since we are using this tool in production for daily feeds, restarting the task whenever something issues arises is not a good idea.

Coming to the SQL server, again one time loads are fine with minor problems but live replication needs too many functions on the SQL server like CDC, Replication etc.

Since Our SQL servers are on AlwaysOn tech, adding replication to the server will add load, increases latency and requires more man power to fix the replication issues. Always on is more advanced feature than replication with less maintenance than replication.

Are there any alternative tools to avoid all these problems? something like AWS Glue, AWS data pipeline, any other third party tools.