A company must migrate 60 on-premises legacy Windows applications built on the .NET Framework to AWS. The company wants to minimize migration time, avoid any application code changes, and not manage underlying infrastructure. Which migration approach meets these requirements?

The correct approach is to use the Windows Web Application Migration Assistant to migrate applications to AWS Elastic Beanstalk. This directly addresses the requirements to minimize migration time and avoid application code changes, as the assistant helps prepare the applications for migration without refactoring. Elastic Beanstalk then provides a fully managed platform, eliminating the need to manage underlying infrastructure. Refactoring and containerizing applications (whether on ECS or EKS) would involve code changes and additional development effort, violating the "no application code changes" and "minimize migration time" requirements. Migrating to EC2 instances would require managing the underlying infrastructure, which the company wants to avoid.