aws dms troubleshooting
aws dms troubleshooting

Also read RDS Deep Dive

Enable Cloudwatch Logs for your DMS Task

This is a simple checkbox in the ‘modify’ section of your DMS Task. This is the ONLY way you can get insight into what’s happening during the migration. YOu may encounter a ‘missing role’ error when you try to VIEW the cloudwatch logs (see below).

Cannot See Cloudwatch Logs? Error on View Logs?

First, enable CloudWatch logging for your task, if you haven’t already. To enable CloudWatch logging, your task must be in a Stopped or Failed state.

If CloudWatch logging is enabled for your task and you still can’t view the logs, confirm that you have the required IAM role. Open the IAM console, and then choose Roles from the navigation pane. Confirm that dms-cloudwatch-logs-role is listed. If you created the task using the AWS Command Line Interface (AWS CLI) or the dms-cloudwatch-logs-role role wasn’t created because the account doesn’t have sufficient permissions, then create the role with the required policies using the AWS CLI or follow these steps:

1.    Open the IAM console, and then choose Roles from the navigation pane.

2.    Choose Create role.

3.    Choose AWS service from Select type of trusted entity. Doing so allows the AWS service in the next step to perform actions on your behalf.

4.    Choose DMS from Choose a use case, which creates the following trust relationship policy so that AWS DMS can assume the role:

{  
"Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "",
      "Effect": "Allow",
      "Principal": {
       
    "Service": "dms.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

5.    Choose Next: Permissions.

6.    Enter AmazonDMSCloudWatchLogsRole in the search field. Then, choose the policy to grant AWS DMS access to CloudWatch.

7.    Choose Next: Tags.

8.    Optionally, add metadata to the role by using tags as key-value pairs.

9.    Choose Next: Review.

10.    For Role name, enter dms-cloudwatch-logs-role.

11.    Role description is filled, and you can add or edit the description as needed.

12.    Chose Create role.

Advanced Queries (Filtering for errors) – Using Log Insights

Click on the ‘Log Insights’ tab (a new feature). To get advanced insights, for example, to see all ERRORS in your DMS logs, run the following in the ‘Log Insights’ Query window.

filter @logStream = 'dms-task-ABCDEFSSSSdfadfadfadw2e3e' 
| fields @timestamp, @message like /Error/

Summary

This is just a quick recap of some commonly encountered issues – and aws dms troubleshooting.

Anuj holds professional certifications in Google Cloud, AWS as well as certifications in Docker and App Performance Tools such as New Relic. He specializes in Cloud Security, Data Encryption and Container Technologies.

Initial Consultation

Anuj Varma – who has written posts on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

 Twitter Linkedin