Please share with the community what you think needs improvement with AWS Database Migration Service.
What are its weaknesses? What would you like to see changed in a future version?
I think that Amazon needs to improve the migration scenarios after analytics. We need more migration tools or more specific tools for migration and licenses. It's a very complicated scenario because, in some cases, we need specific licenses to create new instances, and some instances are very expensive. That's a very manual scenario.
There is something where AWS Database Migration can be improved. Many of the application teams don't want to invest on a migration. They don't want to use the Database Migration service. They want us to export to the dump point, database backup, and then put it into the RDS. There is not a cast and mold on it except in the database and that's it. So migrating from here and pushing the data from on-premise to AWS cloud is a big challenge, and a few more services from AWS would be helpful. For example, currently we are using ILDB internet tools which move data from on-premise to AWS cloud. I need a few more services which would be really helpful for me to move the master data.
The pricing can be better and it should be more competitive, so I would like to see an improvement there.
It would be helpful if the bandwidth could be independent of the network or if we could have a dedicated bandwidth for this product. In terms of dedicated bandwidth, if it can be support Excel or prioritize Excel based on the data it is going to transfer, it would be better.
There's some functionality that we're waiting on, like the problem scheduler. It's not yet supported in the current product. The solution could use schedule linking. I'm keen to get that from the solution in the future.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.