AWS App2Container now supports remote execution of containerization workflows
AWS App2Container (A2C) now supports remote execution of containerization Workflow. With this feature, users can now direct A2C workflows that need to be run on an application server (where applications are deployed) remotely. This is done without directly logging into the application server. Ability to run some of the containerization workflows remotely, has been supported in previous releases. With this new feature, users can now use a remote machine as a single place to run all A2C workflows interacting with applications running on different application servers. This eliminates the need for installing A2C on each application server.
AWS App2Container (A2C) now supports remote execution of containerization Workflow. With this feature, users can now direct A2C workflows that need to be run on an application server (where applications are deployed) remotely. This is done without directly logging into the application server. Ability to run some of the containerization workflows remotely, has been supported in previous releases. With this new feature, users can now use a remote machine as a single place to run all A2C workflows interacting with applications running on different application servers. This eliminates the need for installing A2C on each application server.
AWS App2Container (A2C) is a command-line tool for modernizing .NET and Java applications into containerized applications. A2C analyzes and builds an inventory of all applications running in virtual machines, on-premises or in the cloud. You simply select the application you want to containerize, and A2C packages the application artifact and identified dependencies into container images, configures the network ports, and generates the ECS task and Kubernetes pod definitions.
To learn more, refer to App2Container technical documentation.