If the application server meets all the prerequisites and can run all the AWS App2Container (A2C) tasks, follow the instructions in the App2Container documentation.

If the application server can’t run all the App2Container tasks, use a worker machine. Split the App2Container tasks between the application server and the worker machine.

On the application server, you install and initialize App2Container. Then you analyze the Java applications that are running on the application server. The analysis generates the analysis.json file. Then generate the archive and upload it to an Amazon Simple Storage Service (Amazon S3) bucket or manually copy the archive to the worker machine.

On the worker machine, containerize the application to generate a Docker image. Based on the application type, App2Container takes a conservative approach, known as process mode, to identify dependencies. In process mode, all nonsystem files on the application server are included in the container image. In such cases, it is possible that a large image is generated. Then deploy the application to Amazon ECS or Amazon EKS. During containerization, a deployment.json file is created, which is then used by the generate-app-deployment command.https://docs.aws.amazon.com/prescriptive-guidance/latest/containerize-java-a2c/containerize.html