Developers
July 27, 2020

AWS Introduces a New Containerizing Tool for Java and .NET Applications

AWS App2Container provides seamless deployment to AWS EC2 and EKS. Building and deploying containerized applications can be easier now.

AWS is launching a new command-line tool that can help containerize existing on-premises applications running in AWS EC2, or in other clouds. More and more customers are using containers and serverless technologies to develop their applications. They also use continuous integration and delivery tools to automate the software development cycle. 

Developers maintain their existing applications with tools that are inefficient and cause operational slowdowns. There is a need to standardize the management tooling for applications.

The problem with containerizing applications is that there is a requirement of long manual tasks that are time-consuming and slow down even more the whole process. You have to identify application dependencies, write dockerfiles, and set up build and deployment processes. 

To solve the problem, Amazon announced it is launching AWS App2Container. It is a new command-line tool that helps containerize applications that run in Amazon Elastic Compute Cloud or other cloud services.

What does App2Container do?

App2Contariner discovers applications that are running on a server, it identifies their dependencies and generates the necessary artifacts to be deployed on Amazon ECS and Amazon EKS. The service provides integration with AWS CodeBuild and AWS CodeDeploy.

App2Container generates some artifacts for the application components, including Application artifacts such as application folders, Dockerfiles, container images Elastic Container Registry, Kubernetes deployment YAML, and CloudFormation templates.

From today on, you can use App2Container to containerize ASP.NET web applications running on Windows and Java applications running on Linux. When you modernize an existing application by the use of a container, you transform it into a portable application, meaning a more agile application with lower operational costs.

To get started there are a couple of requisites for the server. AWS Command Line Interface, Docker tools, and IAM permissions have to be installed and working for App2Container to run.

When setting up the workspace to store the application, you can extract the artifacts into your Amazon Simple Storage Service, also known as the S3 bucket. You can do this using your AWS profile.

To check Java processes that are running on the application server you can use the inventory command. Each Java application process counts with a unique identifier. You can use the ID to refer to any application process.

You can initialize your ASP.NET applications on an administrator-run PowerShell session of Windows Servers. You can run all your App2Container operations on the application server that have Docker tools installed.

Commands

By using the inventory command, you can display all the IIS websites that belong to the application server that can be containerized. The Iid website processes have unique identifiers too, IDs. You can use these IDs to refer to the application.

By using the analysis command you can choose a specific application and generate an analysis report. You can use the analysis.json template that is generated by the application analysis to generate information that can help you identify system dependencies. By using the extract command, you can continue the workflow on a worker machine after it runs the first set of commands on the application server.

By using the docker run command, you can view the generated container images that are using Docker images. By using the command it launches the container and tests the application functionality.  

Despite the generation of container images, the containerize command also generates a deployment.json template file. You can edit the parameters in the deployment.json template file and change the repository name.

You can edit the Dockerfile generated to make changes to the application. By using the docker build command you can build new container images on demand. By using the generate-deployment command, you can generate the needed artifacts to deploy the application containers on Amazon EKS. 

The deployment.json template file is produced as part of the containerize command. App2Container generates ECS EKS cloud formation templates and the option to deploy the stacks.  

When containerizing ASP.NET applications, the same process applies to Java applications. The difference is that Windows containers cannot be directly joined. You can still use active directory domain identities to support authentication.  

AWS App2Container is offered for free. Based on the Amazon pricing policy, you only pay for what you use. The same applies to other services and the most used ones such as EC2, ECS, EKS, and S3. If you want to dive deeper into App2Container, you can check out the Frequently asked questions and the documentation.

In conclusion, Amazon introduces AWS App2Container, a containerizing tool for Java and ASP.NET applications. It solves the manual process of containerizing an application. The time taking and ineffective process of containerizing an application is replaced by a service that is ready to be used. We have explained the most used commands and their uses throughout the article so you can know what the service is up to. The service is priced as you pay for what you use. To know more about the service, please check out the documentation.

TagsAWSContainersServerlessApp2Container
Lucas Bonder
Technical Writer
Lucas is an Entrepreneur, Web Developer, and Article Writer about Technology.

Related Articles

Back
DevelopersJuly 27, 2020
AWS Introduces a New Containerizing Tool for Java and .NET Applications
AWS App2Container provides seamless deployment to AWS EC2 and EKS. Building and deploying containerized applications can be easier now.

AWS is launching a new command-line tool that can help containerize existing on-premises applications running in AWS EC2, or in other clouds. More and more customers are using containers and serverless technologies to develop their applications. They also use continuous integration and delivery tools to automate the software development cycle. 

Developers maintain their existing applications with tools that are inefficient and cause operational slowdowns. There is a need to standardize the management tooling for applications.

The problem with containerizing applications is that there is a requirement of long manual tasks that are time-consuming and slow down even more the whole process. You have to identify application dependencies, write dockerfiles, and set up build and deployment processes. 

To solve the problem, Amazon announced it is launching AWS App2Container. It is a new command-line tool that helps containerize applications that run in Amazon Elastic Compute Cloud or other cloud services.

What does App2Container do?

App2Contariner discovers applications that are running on a server, it identifies their dependencies and generates the necessary artifacts to be deployed on Amazon ECS and Amazon EKS. The service provides integration with AWS CodeBuild and AWS CodeDeploy.

App2Container generates some artifacts for the application components, including Application artifacts such as application folders, Dockerfiles, container images Elastic Container Registry, Kubernetes deployment YAML, and CloudFormation templates.

From today on, you can use App2Container to containerize ASP.NET web applications running on Windows and Java applications running on Linux. When you modernize an existing application by the use of a container, you transform it into a portable application, meaning a more agile application with lower operational costs.

To get started there are a couple of requisites for the server. AWS Command Line Interface, Docker tools, and IAM permissions have to be installed and working for App2Container to run.

When setting up the workspace to store the application, you can extract the artifacts into your Amazon Simple Storage Service, also known as the S3 bucket. You can do this using your AWS profile.

To check Java processes that are running on the application server you can use the inventory command. Each Java application process counts with a unique identifier. You can use the ID to refer to any application process.

You can initialize your ASP.NET applications on an administrator-run PowerShell session of Windows Servers. You can run all your App2Container operations on the application server that have Docker tools installed.

Commands

By using the inventory command, you can display all the IIS websites that belong to the application server that can be containerized. The Iid website processes have unique identifiers too, IDs. You can use these IDs to refer to the application.

By using the analysis command you can choose a specific application and generate an analysis report. You can use the analysis.json template that is generated by the application analysis to generate information that can help you identify system dependencies. By using the extract command, you can continue the workflow on a worker machine after it runs the first set of commands on the application server.

By using the docker run command, you can view the generated container images that are using Docker images. By using the command it launches the container and tests the application functionality.  

Despite the generation of container images, the containerize command also generates a deployment.json template file. You can edit the parameters in the deployment.json template file and change the repository name.

You can edit the Dockerfile generated to make changes to the application. By using the docker build command you can build new container images on demand. By using the generate-deployment command, you can generate the needed artifacts to deploy the application containers on Amazon EKS. 

The deployment.json template file is produced as part of the containerize command. App2Container generates ECS EKS cloud formation templates and the option to deploy the stacks.  

When containerizing ASP.NET applications, the same process applies to Java applications. The difference is that Windows containers cannot be directly joined. You can still use active directory domain identities to support authentication.  

AWS App2Container is offered for free. Based on the Amazon pricing policy, you only pay for what you use. The same applies to other services and the most used ones such as EC2, ECS, EKS, and S3. If you want to dive deeper into App2Container, you can check out the Frequently asked questions and the documentation.

In conclusion, Amazon introduces AWS App2Container, a containerizing tool for Java and ASP.NET applications. It solves the manual process of containerizing an application. The time taking and ineffective process of containerizing an application is replaced by a service that is ready to be used. We have explained the most used commands and their uses throughout the article so you can know what the service is up to. The service is priced as you pay for what you use. To know more about the service, please check out the documentation.

AWS
Containers
Serverless
App2Container
About the author
Lucas Bonder -Technical Writer
Lucas is an Entrepreneur, Web Developer, and Article Writer about Technology.

Related Articles