Hi! Looking at the docs https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/dms_replication_task there is a note which seems relevant:
NOTE: Changing most arguments will stop the task if it is running. You can set start_replication_task to resume the task afterwards.
Unfortunately, the docs don't indicate the type of the parameter so I suggest you look at your state to see if it should be
start_replication_task = true or something else.
Hope this helps!
Whenever you Stop and Resume an AWS DMS task, it resumes from the position where it was paused. Meaning, if you resume the task after X minutes, AWS DMS task will try to get the changes since it was paused by reading the Binary Logs. Looking at the error, it looks like the task was not able to find the required Binary Logs to resume the replication.
If you happen to Stop the DMS task, make sure that the DB host has all the required Binary Logs available so that the task can be successfully resumed.
DMS and Terraformasked 11 days ago
DMS replication task not generate a operation columnasked a month ago
Using DMS and SCT for extracting/migrating data from Cassandra to S3asked 5 months ago
Do source filters speed up DMS from AWS RDS to S3?asked 9 months ago
DMS: How does a replication task handle duplicate data w/o Primary/Unique keys on the tableasked 3 months ago
Does DMS drop and creates the target files in S3 target endpoints?asked 2 months ago
DMS CDC - MySQL Binlog Precision - Seconds to Microsecondsasked 2 months ago
AWS DMS Migration task from source MongoDB and target RDS Postgresasked 3 months ago
DMS task is creating full row duplicates in targetasked 7 months ago
AWS DMS migration task doesn't automatically increment the source tableAccepted Answerasked 2 years ago