AWS Schema Conversion Tool vs YugabyteDB Voyager

AWS Schema Conversion Tool (AWS SCT) converts database schemas between engines, including relational OLTP, data warehouse, and NoSQL schemas. If it cannot automate a conversion, it gives guidance for creating an equivalent schema in the target database. A project wizard estimates migration complexity for supported destinations and generates a report for comparing target options. For warehouse migrations to Amazon Redshift, it can manage data extraction agents; it can also create, run, and monitor AWS DMS endpoints and tasks. AWS SCT converts SQL embedded in C++, C#, Java, and other application code for users to review, edit, and save. Supported workload conversions include SSIS packages, Teradata workloads, and Apache Oozie workflows to specified AWS services. It is both a standalone, project-based application and a command-line tool. Planned converted schemas stay local until applied to the target. AWS SCT is free and supports 64-bit Microsoft Windows, Fedora Linux, and Ubuntu Linux. It also supports FIPS standards for connections to Amazon S3 or another AWS resource and is compliant with FedRAMP.

YugabyteDB Voyager has no write-up on Specifiction yet; its figures are above.