Which solution will meet these requirements?
Use AWS Database Migration Service (AWS DMS) to migrate all database objects from the on-premises SQL Server database to a Multi-AZ deployment of Amazon Aurora MySQL.
Use AWS Database Migration Service (AWS DMS) and the AWS Schema Conversion Tool (AWS SCT) to migrate all database objects from the on-premises SQL Server database to a Multi-AZ deployment of Amazon Aurora MySQL.
Rehost the on-premises SQL Server as a SQL Server Always On availability group. Host members of the availability group on Amazon EC2 instances. Use AWS Database Migration Service (AWS DMS) to migrate all database objects.
Rehost the on-premises SQL Server as a SQL Server Always On availability group. Host members of the availability group on Amazon EC2 instances in a single subnet that extends across multiple Availability Zones. Use SQL Server tools to migrate the data.
Explanations:
AWS Database Migration Service (DMS) can migrate data but does not handle the migration of database objects like secondary indexes and stored procedures. Also, Amazon Aurora MySQL may not fully support all features of SQL Server, leading to potential compatibility issues.
AWS DMS can handle data migration, while the AWS Schema Conversion Tool (SCT) can help migrate database schema, including secondary indexes and stored procedures, to Amazon Aurora MySQL. Aurora MySQL can be deployed in a Multi-AZ configuration, providing high availability.
Rehosting SQL Server on EC2 instances using Always On availability groups would not fully meet the requirement of modernizing the application. This solution requires significant management overhead for database specialists and does not reduce operational costs or automate the migration.
Rehosting SQL Server on EC2 instances using Always On availability groups in a single subnet does not address the need for modernizing the application. SQL Server tools for migration are manual, requiring database specialists, which contradicts the requirement for limited support.