As an AWS Partner, we are very excited for the new capabilities that AWS App2Container (A2C) gives us, to help our customers take the first steps towards modernizing legacy applications without the need for any refactoring. Many of our customers don’t know where to start with containerization, and A2C provides a first-class, prescriptive path to quickly move ASP .net and Java applications from legacy VM-based hosting to containers. Engineers and Solutions Architects who use the AWS CLI, will find the A2C CLI to be familiar and intuitive. The documentation is clear, and covers containerizing both Linux and Windows application servers.
One key feature of A2C is its ability to be run as a standalone worker node, to containerize workloads in a non-intrusive fashion, without the need for installing potentially disruptive agents on production servers. A2C also supports Amazon ECR, ECS, and EKS, so that businesses can quickly see and test their legacy apps hosted in the cloud. Teams using Kubernetes can use kubectl to launch the containerized application on an existing Amazon EKS or self-managed Kubernetes cluster using A2C generated deployment.yaml. A2C even supports running containerized workloads under a Group Managed Service Account (gMSA), which is an advanced concept for containerizing Windows apps that our team was pleasantly surprised to find A2C supports.
In short, A2C is an easy and prescriptive way to take the first steps towards modernizing legacy applications, without the need for any refactoring. Any shop running legacy ASP.NET and/or Java applications should consider A2C as a critical tool to streamline and accelerate their application modernization journey on AWS.