Skip to content

DMS Premigration Assessment fails with error-provisioning for GCP Cloud SQL source endpoint

0

Issue: When running a premigration assessment on our DMS migration task that uses a GCP Cloud SQL instance as the source endpoint, the assessment run consistently fails with error-provisioning status and the following error message:

DMS was unable to get information about source endpoint's version and edition. Status code: 400

Environment:

AWS Region: eu-central-1

Source Endpoint: GCP Cloud SQL (tried with MySQL 8.0 and 8.4)

Target Endpoint: Amazon RDS (MySQL 8.4)

Migration Type: CDC only (GCP Cloud SQL MySQL to AWS RDS MySQL)

DMS Version: 3.5.4

What We Have Already Checked:

Endpoint connectivity test passes — The "Test connection" for the source endpoint succeeds without any errors. So network connectivity, credentials, CA certificates, IAM and security group configuration are all correct. The DMS user has full global privileges (GRANT SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAV, REPLICATION CLIENT, SHOW VIEW ON *.* TO 'dms_user'@'%') The Cloud SQL instance has public IP with firewall rules but the replication instance's IP is added into its Authorized networks.

The endpoint account can retrieve VERSION() = '8.0.46-google' and @@version_comment = '(Google)' and read all documented assessment metadata tables.

No results written to S3 — The configured S3 bucket contains no summary.json or any assessment result files, confirming the assessment fails before any individual checks are executed. The IAM role assigned to the assessment run has been verified and contains the correct s3:PutObject , s3:GetObject, and s3:ListBucket permissions for the assessment report bucket. No logs for the replication instance in CloudWatch.

Source endpoint config — We have tried MySQL and Google Cloud SQL for MySQL as Source engine for the endpoint with MySQL version 8.0 and 8.4 resulting in the same error message. We tried targetDbType=SPECIFIC_DATABASE in extra Connection Attributes (ECA) and in Endpoint settings (TargetDbType: "specific-database") as suggested Amazon Q but that did not work.

Questions:

Is this a known limitation of using GCP Cloud SQL as a DMS source endpoint for premigration assessments?

Is there a workaround to allow the premigration assessment to run while skipping the version/edition check during provisioning?

Please inspect the backend discovery failure and confirm whether a patch or engine upgrade resolves it.

asked a month ago134 views

1 Answer
0

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:

  1. 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.

  2. 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

answered a month ago

EXPERT

reviewed a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.