- Newest
- Most votes
- Most comments
The error-provisioning status you're encountering indicates an internal error occurred while AWS DMS was provisioning the resources required to run individual assessments. The specific error message about being unable to get information about the source endpoint's version and edition with a 400 status code suggests that DMS is having difficulty querying metadata from your GCP Cloud SQL instance during the assessment setup phase.
While your endpoint connectivity test passes successfully, premigration assessments require additional metadata queries beyond basic connectivity. The assessment provisioning phase attempts to gather detailed information about the source database's version and edition to determine which individual assessments to run. This metadata collection appears to be failing when DMS queries the GCP Cloud SQL instance.
Since you've confirmed that your DMS user has the necessary privileges (SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT, SHOW VIEW) and network connectivity is working, the issue likely stems from how GCP Cloud SQL responds to certain metadata queries that AWS DMS makes during assessment provisioning. GCP Cloud SQL may handle or restrict certain system queries differently than native MySQL instances or Amazon RDS.
Regarding your questions:
-
While GCP Cloud SQL is a supported source for AWS DMS migrations, there may be specific limitations or compatibility issues with the premigration assessment feature when used with GCP Cloud SQL. The assessment framework may expect certain MySQL system tables or information schema queries to behave in ways that differ from GCP's implementation.
-
Unfortunately, there isn't a documented way to skip the version/edition check during assessment provisioning or to bypass specific provisioning steps. The assessment run must complete the provisioning phase before it can execute individual assessments.
As a potential path forward, you might consider:
- Proceeding with your CDC migration without running the premigration assessment, since your endpoint connectivity is confirmed and your DMS user has the required permissions
- Monitoring your migration task closely during the initial phases using CloudWatch metrics and task logs
- Reviewing your AWS Support plan options if you need assistance investigating this specific compatibility issue with GCP Cloud SQL
If you need further investigation into this issue, you can add correspondence about this behavior through the AWS Support Center at https://console.aws.amazon.com/support/.
Sources
PremigrationAssessmentStatus - AWS Database Migration Service
PremigrationAssessmentStatus.Builder (AWS SDK for Java - 2.42.38)
Troubleshoot task failures, such as indefinite running, error states, and progress visibility issues in AWS DMS | AWS re:Post
Relevant content
asked 2 years ago
asked 2 years ago
asked 2 years ago
