Which solution will meet these requirements?
Refactor the applications and containerize them by using AWS Toolkit for NET Refactoring. Use Amazon Elastic Container Service (Amazon ECS) with the Fargate launch type to host the containerized applications.
Use the Windows Web Application Migration Assistant to migrate the applications to AWS Elastic Beanstalk. Use Elastic Beanstalk to deploy and manage the applications.
Use the Windows Web Application Migration Assistant to migrate the applications to Amazon EC2 instances. Use the EC2 instances to deploy and manage the applications.
Refactor the applications and containerize them by using AWS Toolkit for NET Refactoring. Use Amazon Elastic Kubernetes Service (Amazon EKS) with the Fargate launch type to host the containerized applications.
Explanations:
Refactoring and containerizing applications is not required, as the company does not want to make code changes.
The Windows Web Application Migration Assistant is a suitable tool for migrating legacy Windows apps to AWS Elastic Beanstalk, which handles deployment and management without code changes.
Migrating to EC2 instances requires managing the infrastructure, which is not in line with the requirement to avoid infrastructure management.
Containerizing and refactoring the applications is unnecessary, and AWS Fargate with Amazon EKS would still require application code changes.
I suspect that the answer is:
Use the Windows Web Application Migration Assistant to migrate the applications to AWS Elastic Beanstalk. Use Elastic Beanstalk to deploy and manage the applications.
I judge that the answer is:
Use the Windows Web Application Migration Assistant to migrate the applications to AWS Elastic Beanstalk. Use Elastic Beanstalk to deploy and manage the applications.