Question

A financial services company runs a legacy .NET Framework application on Windows Server 2012 EC2 instances behind an internal load balancer. The application is a monolith that has no source code changes anymore and the original developers have left. Leadership wants to modernize the deployment to reduce OS patching overhead and improve density, ideally moving to containers without rewriting the application. The team has minimal container expertise and needs a repeatable, low-effort path to containerize the running application and generate the necessary deployment artifacts. Which approach best meets these requirements?

Accepted Answer

Use AWS App2Container (A2C) to discover the running application, containerize it into a Windows container image, and generate ECS/EKS deployment artifacts and a CI/CD pipeline template.

Answer

Use AWS Application Migration Service (MGN) to replicate the EC2 instances, then manually write Dockerfiles to package the application into containers after cutover.

Answer

Rewrite the monolith as ASP.NET Core microservices running on AWS Fargate, decomposing functionality by business domain before migrating.

Answer

Use AWS Elastic Beanstalk with the .NET on Windows platform to deploy the application without any code changes and let it manage the underlying instances.