Troubleshooting for homogeneous data migrations in AWS DMS
In the following list, you can find actions to take when you encounter issues with homogeneous data migrations in AWS DMS.
Topics
I can't create a homogeneous data migration in AWS DMS
If you get an error message that says that AWS DMS can't connect to your data providers after you choose Create data migration, then make sure that you have configured the required IAM role. For more information, see Creating an IAM role.
If you have configured the IAM role and still get this error message, then add this IAM role to your key user in the AWS KMS key configuration. For more information, see Allows key users to use the KMS key in the AWS Key Management Service Developer Guide.
I can't start a homogeneous data migration in AWS DMS
If you get the Failed status when you start a data migration in your migration project,
check the versions of your source and target data providers. To do so, run the SELECT VERSION();
query in your MySQL or PostgreSQL database. Make sure that you use the supported database version.
For the list of supported source databases, see Sources for DMS homogeneous data migrations.
For the list of supported target databases, see Targets for DMS homogeneous data migrations.
If you use an unsupported database version, then upgrade your source or target database, and try again.
Check the error message for your data migration in the AWS DMS console. To do so, open your migration project, and choose your data migration. On the Details tab, check the Last failure message under General.
Finally, analyze the CloudWatch log. To do so, open your migration project, and choose your data migration. On the Details tab, choose View CloudWatch logs.
I can't connect to the target database when running a data migration in AWS DMS
If you get the Unable to connect to target error message, then perform the following actions.
Make sure that the security group that is attached to your source and target databases contains a rule for any inbound and outbound traffic. For more information, see Configuring ongoing data replication.
Verify the network access control list (ACL) and route table rules.
Your database must be accessible from the VPC that you created. Add public IP addresses in VPC security groups, and allow input connections in your firewall.
On the Data migrations tab of your migration project, choose your data migration. Take a note of the public IP address under Connectivity and security on the Details tab. Next, allow access from the public IP address of your data migration in your source and target databases.
For ongoing data replication, make sure that your source and target databases can communicate with each other.
For more information, see Control traffic to resources using security groups in the Amazon Virtual Private Cloud User Guide.
AWS DMS migrates views as tables in PostgreSQL
Homogeneous data migration doesn't support migrating views as views in PostgreSQL. For PostgreSQL, AWS DMS migrates views as tables.
