Skip to content

"Schema Migration Actions Not Available in AWS DMS Schema Conversion Project (RDS MySQL to RDS PostgreSQL)"

0

I am using AWS DMS Schema Conversion to migrate schemas from RDS MySQL (source) to RDS PostgreSQL (target).

  • I have completed the following setup steps:
    • Created the required instance profile and IAM permissions
    • Added data sources for both RDS MySQL and RDS PostgreSQL
    • Created a schema migration project
    • Launched the schema conversion process

However, I am unable to use the Actions button in the DMS Schema Conversion project, which is preventing me from proceeding with the migration workflow (e.g., generating or applying converted schema). When I deleted and recreated the project, the Schema Conversion feature is no longer visible in the AWS DMS console.

Questions:

  • What could cause the Actions button to be unavailable in an active schema migration project?
  • Are there known prerequisites, user permissions, or service limits that could prevent the Actions menu from being active?
  • Why would the Schema Conversion feature disappear from the DMS console after recreating the migration project?
  • Are there any recent changes to the AWS DMS Schema Conversion UI or service availability that could explain this behavior?
  • How can I restore access to the schema conversion functionality and proceed with my RDS MySQL to RDS PostgreSQL migration?

Any insights, troubleshooting steps, or similar experiences would be greatly appreciated. Thank you!Enter image description here

1 Answer
0

Based on the information provided, there are several potential reasons why you might be experiencing issues with the Actions button in AWS DMS Schema Conversion:

  1. Selection of schema objects: To activate the Actions menu, you need to first select the schema name in the source database pane. The Actions menu becomes active only after you've selected a schema or database object. Make sure you've selected the schema name in the left pane of the migration project, which should highlight it in blue and activate the Actions menu.

  2. Metadata loading: The schema information in DMS Schema Conversion is lazy loaded. You might need to explicitly load the metadata before you can perform actions. Look for a "Load metadata" option in the interface.

  3. Region availability: DMS Schema Conversion might not be available in all AWS regions. The generative AI capabilities for schema conversion, for example, are only available in US East (N. Virginia), US West (Oregon), and Europe (Frankfurt) regions. Check if you're working in a supported region.

  4. Service limitations: DMS Schema Conversion is a web version of AWS Schema Conversion Tool (SCT) with more limited functionality. It has several limitations compared to the standalone AWS SCT desktop application, including:

  • No offline mode
  • No ability to edit SQL code for the source in a migration project
  • Limited migration rule support
  • No filters for database trees
  • No extension pack with Lambda functions
  1. Database version compatibility: Ensure your MySQL version is supported by DMS Schema Conversion. Some older database versions may not be compatible with the service.

For the disappearance of the Schema Conversion feature after recreating the project, this could be due to:

  • A temporary service issue
  • Region selection during recreation
  • Changes in IAM permissions or roles
  • Console caching issues

To restore access and proceed with your migration:

  1. Clear your browser cache and try accessing the console again
  2. Verify you're in a region where DMS Schema Conversion is available
  3. Double-check your IAM permissions
  4. Consider using the standalone AWS SCT desktop application if DMS Schema Conversion continues to have issues
  5. Contact AWS Support if the problem persists

If the web version continues to present challenges, remember that you can always use the standalone AWS SCT desktop application, which offers more comprehensive functionality for schema conversion before using DMS for the actual data migration.
Sources
Converting database schemas in DMS Schema Conversion - AWS Database Migration Service
Converting database schemas using DMS Schema Conversion - AWS Database Migration Service
AWS Database Migration Service now automates time-intensive schema conversion tasks using generative AI | AWS News Blog

answered 8 months ago
  • i have tried selecting different schema objects still it was not working

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.