Connect to your Worker Machine as explained in Connecting your Windows Instances section.
Open a web browser and Download the AWSApp2Container Windows installer to your server from the following location : https://app2container-release-us-east-1.s3.us-east-1.amazonaws.com/latest/windows/AWSApp2Container-installer-windows.zip
The Installer file will be downloaded into “Downloads” folder. Navigate to “Downloads folder” and extract “AWSApp2Container-installer-windows.zip” file.
Run “install.ps1” powershell script and enter “R” when prompted by the command output. Then press “y” to accept terms and conditions
(optional) Familiarize yourself with the available command for App2Container
The init command performs one-time initialization tasks for App2Container. This interactive command prompts for the information required to set up the local App2Container environment.
If you’ve already created an S3 bucket in “Modernize your Java App” section, you can reuse the same bucket and you can skip this step.
Navigate to the S3 console and enter a unique name for your bucket (app2container-<Your-Initials>-<Date>) and click create and store the name of the bucket in a notepad (this will be required in subsequent steps)
On the worker Machine initialize app2container with “app2container init” command.
You are prompted to provide the following information:
|Workspace directory path||Leave Default. (A local directory where App2Container can store artifacts during the containerization process. The default is C:\Users\Administrator\AppData\Local\app2container.)|
|AWS profile||Leave Default. (Contains information needed to run App2Container, such as your AWS access keys.)|
|Amazon S3 bucket||Enter the Amazon S3 bucket name (app2container-Your-Initials-Date) you’ve created in previous step. (e.g. sd-jan-29)|
|Permission to collect usage metrics||Leave Default. (this option is to allow App2Container to collect information about the host operating system, application type, and the app2container commands that you run.)|
|Whether to enforce signed images||Leave Default. (You can optionally require that images are signed using Docket Content Trust (DCT))|
Ensure to enter the Amazon S3 bucket name (app2container-Your-Initials-Date) you’ve created in previous step once prompted. See example output below.
You need to run “remote configure” command from a worker machine to configure the connections needed to run remote workflows on application servers. This interactive command prompts for the required information for each application server that you enter.
|Server IP Address||Value|
|Server IP Address||Source Server (Source-NET-Webserver) Private IP Address. (You can find from EC2>Source-NET-Webserver> Details> Private IPv4 addresses)|
|Server FQDN||Leave blank|
|Secret ARN||ARN for Secret you’ve created on AWS Secrets Manager earlier|
|Continue to configure another server ?||n|
Copy the Private IP address of the Web Server to your notepad, you will use it in the following sections.
app2container remote configure
You can configure multiple servers at this step for large scale projects.
Congrats! You have now installed and initialize the App2container on your Worker Machine and ready to start containerizing your .NET application via remotely running the app2container process without directly touching your source application server.