Amazon Web Services (AWS) has announced that its AWS Database Migration Service, which was earlier available as preview, is now available to all AWS customers.
The AWS Database Migration Service has seen over 1,000 databases from the likes of Expedia and Pegasystems already complete the move over to its AWS cloud since January 1, 2016.
Amazon states,
“Amazon Web Services, Inc. (AWS), an Amazon.com company (NASDAQ:AMZN), today announced that the AWS Database Migration Service, a fully managed service that allows customers to migrate their production Oracle, SQL Server, MySQL, MariaDB, and PostgreSQL databases from on-premises datacenters to AWS with virtually no downtime, is now available to all customers. Customers, including global enterprises and startups from a range of industries, used the AWS Database Migration Service preview to move more than 1,000 databases to the AWS Cloud since January 1, 2016. Many of these customers also used the AWS Schema Conversion Tool to switch database engines and break free from the cost and complexity of old guard commercial databases. “
To know more about the AWS Database Migration Service, visit https://aws.amazon.com/dms.
As per AWS, the migration service is a completely managed service, which allows customers to migrate their production Oracle, SQL Server, MySQL, MariaDB, and PostgreSQL databases from on-premises datacentres to AWS' cloud.
Hal Berenson, Vice President, Relational Database Services, AWS, states,
“Hundreds of customers moved more than a thousand of their on-premises databases to Amazon Aurora, other Amazon RDS engines, or databases running on Amazon EC2 during the preview of the AWS Database Migration Service. Customers repeatedly told us they wanted help moving their on-premises databases to AWS, and also moving to more open database engine options, but the response to the AWS Database Migration Service has been even stronger than we expected. In the preview, one-third of the database migrations used the AWS Database Migration Service to not only move databases to the AWS Cloud, but also to switch database engines in the process.”
AWS said that in less than 11 weeks, many customers also used the AWS Schema Conversion Tool in order to switch database engines.
The cloud giant said that previously, migrating a database to the cloud saw the possible loss of revenue from the downtime involved in copying over a database, or the purchasing of expensive migration tools.
