0

I created several Full load, ongoing replication task DMS tasks to copy data from a VPS MySQL server to RDS MySQL, and after some tweaks (time zone config, collations, etc) I was able to get everything working as expected and replicating data effectively.

Yesterday however some tables were truncated in my source MySQL database (TRUNCATE table_name). The table statistics in the DMS task did detect a DDL change as appreciated in the below screenshot:

enter image description here

I was able to get the TRUNCATE commands from the MySQL binlog.

Questions:

  • Is there any way that DMS could have been the culprit in literally truncating my source tables? My tasks don't even have the preparation mode TRUNCATE, I have DO NOTHING.
  • I didn't find any way in the configs or in the docs but, does DMS have a way to affect source tables?

Edit:

I get the feeling that the VPS server got hacked. But I haven't been able to confirm if that's the case.

Edit 2:

Even some tables DMS didn't know about (were not included in the table mappings) got truncated as well.

Luis de Haro
  • 711
  • 1
  • 7
  • 28
  • did you look for new tables or databases created in your VPS server, with data telling you how to ransom your truncated tables? – ysth May 24 '22 at 23:01
  • Yes, I couldn't find anything so far TBH. But the weird thing is that some tables DMS wasn't taking into account for the replication were truncated too. – Luis de Haro May 24 '22 at 23:43

1 Answers1

0

AWS DMS can not update/delete the source. Please also refer to official documentation at: https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html regards, Naveed.

nbqadri
  • 13
  • 3
  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community May 27 '22 at 04:42