- Newest
- Most votes
- Most comments
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:
-
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.
-
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.
-
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.
-
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
- 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:
- Clear your browser cache and try accessing the console again
- Verify you're in a region where DMS Schema Conversion is available
- Double-check your IAM permissions
- Consider using the standalone AWS SCT desktop application if DMS Schema Conversion continues to have issues
- 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
Relevant content
- asked 3 days ago
- AWS OFFICIALUpdated 5 months ago

i have tried selecting different schema objects still it was not working