- Newest
- Most votes
- Most comments
Should note that logging is enabled and all log levels are set to
LOGGER_SEVERITY_DETAILED_DEBUG
and yet no log streams are created. Both endpoints pass connectivity checks. DMS replication instance is almost certainly over provisioned (have run more extensive DMS tasks on other sources with lower tier instance types) and reported instance metrics are very very low.
So logging was failing because when you create DMS resources via Cloudformation the
dms-cloudwatch-logs-role
doesn't exist and won't be created.
https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Security.APIRole.html
Was then bouncing off of errors along the lines of "No suitable plugin found" - i had not yet run the following scripts to support legacy function names:
Hope this info helps someone in the future.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 5 months ago