AWS Database Migration Service customers

Our projections are that we will pay about one quarter of what we were paying in our private infrastructure.

Our appeals processing system, VACOLS, includes 20 million records stored in an Oracle 11g database. The system is more than 20 years old and is in the process of being modernized. During this time, we need to ensure that the data is securely replicated into the cloud for safekeeping. We're using AWS DMS to replicate the database into an RDS Oracle database in AWS GovCloud, in a Multi-AZ deployment. This setup ensures that VACOLS data is preserved, secured, and highly available in the cloud, which is a serious win for VA and for our Veterans, who rely on us for the safeguarding of their information.

We are in the process of migrating some databases to Amazon Aurora. The ease by which we can do this using the AWS Database Migration Service has simplified this process for us and enabled us to accelerate our migration efforts. The ability to closely monitor the process, the detailed logging feature, and the support we received from AWS have given us a great deal of confidence in a successful migration.

We are an early adopter of Amazon Aurora PostgreSQL and used the AWS Database Migration Service to transition TIBCO Cloud Live Apps to Amazon Aurora seamlessly, while it was in production, without our customers noticing any interruption in our service. Amazon Aurora's reliability, security, and fast failover will continue to help us scale Live Apps, giving customers constant access to our service so they can build and run apps quickly and with high availability.

We were in the process of splitting a mission critical database into two instances to improve system performance and reliability. We had to perform this procedure with zero downtime, and AWS Database Migration Service saved us a lot of work. Instead of developing the migration code ourselves, we used DMS for the entire transition. We used the simple, intuitive DMS UI to set up database replication into the new environment, and ran the jobs until we were ready to cut over. The ongoing replication gave us the comfort that our data is available all the time. Amazon DMS improved the efficiency and resiliency of the transition, and has become our tool of choice to get data migration jobs done quickly, easily and reliably.

Faced with the challenge of rapidly growing volumes of data and the need to increase efficiency and deliver results on shorter timelines, we were confronted with unattractive options requiring significant upfront investment in both infrastructure and Oracle license expense. We were intrigued by the possibilities when we first learned about Amazon Aurora from our partner Apps Associates, but the magnitude of effort to migrate legacy PL/SQL code seemed to rule out the feasibility of this approach at the outset. The availability of the AWS Database Migration Service caused us to take another look at this problem, and after a careful evaluation, we demonstrated that the AWS Database Migration Service automated most of the work and dramatically reduced the manual effort involved in the code migration. The AWS Database Migration Service will be a key enabler for our plans to migrate more databases to Amazon Aurora in 2016.

In our testing, the AWS Database Migration Service reduced the manual effort and time required to migrate applications from our stand-alone databases to AWS-powered datastores. Now that the AWS Database Migration Service is generally available, we are going to use it to onboard our customers to AWS so that they can realize value even faster from their Pega 7 platform and strategic applications.

Without the AWS Database Migration Service, we would have had to do a tremendous amount of work to move our MySQL databases between our different AWS accounts. The AWS Database Migration Service will help us complete our database migration with minimal disruption, which would have been impossible for us to do previously without experiencing significant downtime.

When SysAid was facing the challenge of moving a large amount of legacy customers to the cloud, we looked for a smart, efficient way to automate the process. We found that the AWS Database Migration Service was a real time-saver. With the unique need to import both SQL Server and MySQL databases and migrate them into our cloud schema MySQL, while simultaneously performing SysAid version upgrades, we realized that only a tool such as DMS could help us complete the task. We're now performing over 6x more migrations, in a set period of time, than we ever could in the past.

Verizon is helping our customers build a better, more connected life. As part of this journey, we are undergoing a major transformation in our database management approach, moving away from expensive, legacy commercial database solutions to more efficient and cost-effective options. Testing of Amazon Aurora PostgreSQL showed better performance over standard PostgreSQL residing on Amazon EC2 instances, and the AWS Database Migration Service and Schema Conversion Tool were found effective at identifying areas for data-conversion that required special attention during migration.

AWS DMS gave us the fastest path to production, with reliability and scalability to move initial loads and change deltas in an automated manner. This means we now have faster, safer, and more reliable data availability in the cloud for our analytic communities that include Risk & Credit, Segments & Insights for Marketing Campaigns, Customer Experience and Operational Reporting. Important customer insights are now ingested and made available for use in a short period of time. It forms a critical part of our data pipeline and migration from on-prem to cloud native.

We recently completed the migration of all our databases to Amazon Aurora. The migration options provided by DMS gave us more flexibility than regular replication when we migrated our existing MySQL database. This allowed us to dry run our migration process before the final cutover, to ensure everything worked as planned. DMS reporting features allow you to closely monitor each job to track progress, and this gave us the confidence that our data was being migrated correctly to Aurora.