AWS makes Database Migration Service available to all customers
Amazon Web Services has now made its database migration service available to all of its customers, after completing the migration of over 1,000 databases since the first day of 2016. — Amazon Web Services (AWS) …
Context & Ripple Effects
This GA announcement is the tooling layer of AWS's database land-grab: weeks earlier, Amazon had launched an analytics service aimed at non-technical users with a faster method for moving data into AWS, and DMS extends that same on-ramp logic to the hardest part of any cloud switch — the production database. Over 1,000 databases migrated since the first day of 2016 served as the internal proof before the service was opened to everyone.
The arc that follows validates the bet: Amazon's own consumer business later finished decommissioning its final Oracle database, moving 75 petabytes onto AWS services, and by 2024 Oracle itself was selling Oracle Database@AWS inside AWS rather than fighting the migration path.
First-order effects
- Every AWS customer can now run database migrations themselves instead of treating them as bespoke projects — the immediate targets are enterprises sitting on Oracle and Microsoft SQL Server estates whose switching costs just dropped.
- Oracle and Microsoft lose their strongest retention lever at the exact moment a customer evaluates leaving: the migration effort that once protected their installed base becomes a managed AWS checkbox.
Second-order effects
- Competing platforms are pushed to answer with their own migration tooling, while AWS keeps sharpening the wedge — Babelfish for Aurora PostgreSQL later aimed squarely at making SQL Server exits cheaper via T-SQL compatibility.
- Database vendors face a pricing squeeze: when exit friction falls, license renewals have to compete on merit against AWS-native services, shifting negotiation leverage to buyers mid-migration.
Third-order effects
- If the pattern holds, migration tooling becomes table stakes for every cloud, and database choice decouples from infrastructure provider — culminating in former lock-in champions like Oracle distributing their databases inside rival clouds, as the Database@AWS partnership shows.
- The durable shift is from databases as moats to databases as workloads that follow the cheapest credible platform, with the cloud holding the migration pipe capturing the customer relationship either way.
The trend: Cloud providers are converting database migration from a high-friction consulting project into self-service product, steadily eroding incumbent vendors' lock-in until those vendors partner with the very clouds draining their installed base.