1 Answer
- Newest
- Most votes
- Most comments
1
Hi all,
The issue has been sorted out.
It turns out the DMS replication instance was running out of memory, and this is what was coming out in the CloudWatch logs: "Failed to run load command. Cannot allocate memory."
The solution was to scale the DMS instance up to something more memory-efficient, e.g.: dms.r5.2xlarge
Regards,
Vinny Osiro
answered 3 years ago
Relevant content
- Accepted Answerasked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 7 months ago