As an AWS Companion, we are very angry for the new capabilities that AWS App2Container (A2C) presents us, to lend a hand our prospects obtain the first steps in direction of modernizing legacy capabilities with out the need for any refactoring. Many of our prospects don’t know the put to birth out up with containerization, and A2C supplies a top quality, prescriptive route to like a flash switch ASP .acquire and Java capabilities from legacy VM-essentially based mostly hosting to containers. Engineers and Solutions Architects who utilize the AWS CLI, will acquire the A2C CLI to be acquainted and intuitive. The documentation is evident, and covers containerizing each Linux and Windows utility servers.
One key feature of A2C is its skill to be bustle as a standalone employee node, to containerize workloads in a non-intrusive fashion, with out the need for inserting in likely disruptive agents on manufacturing servers. A2C also helps Amazon ECR, ECS, and EKS, so that companies can like a flash look and take a look at their legacy apps hosted within the cloud. Groups the usage of Kubernetes can utilize kubectl to commence the containerized utility on an unusual Amazon EKS or self-managed Kubernetes cluster the usage of A2C generated deployment.yaml. A2C even helps working containerized workloads below a Team Managed Provider Myth (gMSA), which is an superior view for containerizing Windows apps that our workforce became once pleasantly surprised to search out A2C helps.
In transient, A2C is a truly easy and prescriptive arrive to acquire the first steps in direction of modernizing legacy capabilities, with out the need for any refactoring. Any shop working legacy ASP.NET and/or Java capabilities might maybe likely maybe also soundless mediate about A2C as a excessive tool to streamline and trail up their utility modernization lope on AWS.