Simudyne SDK on Windows Server 2022

For a full guide: https://docs.simudyne.com/reference/run_deploy/aws 

1. The first step is to make a few changes to your pom.xml. You'll add the maven and docker shade plugin which allows you to easily package for deployment. For an example of this pom file please refer to: https://docs.simudyne.com/reference/run_deploy/aws#packaging-your-model 

2. Once your pom has been updated you can the package everything into a single jar (allinone) by running 'mvn clean compile package -s settings.xml' inside the project's folder.

Next we'll create our instance. We'll outline the steps below, but you can always refer to the Official AWS Documentation for guidance on setting up a new instance.

3. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/  and select the orange Launch instance button.

4. Set a name for your instance, and then select Windows instance and then search for the Simudyne Amazon Machine Image (AMI).

5. You'll then select the instance type. If you are just trying to deploy for your first time to ensure that everything works, you can use the the r6i selected by default based on your region.

6. Under Key pair (login) select 'Create new key pair' (unlesss you have already created or associated a key pair, or one has been assigned to you)

7. Follow the steps to create a key pair, and make sure to select .pem. You will use this file and follow the steps here from AWS: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/connecting_to_windows_instance.html  to create an RDP file and associated password. You will connect by opening this file on Windows after downloading and using the created password,

8. Under Network Settings unless you have already created a Security Group you will likely want to proceed with the default which will create one for you.

9. If your goal with this deployment is to access the SDK either via the console, or via a dashboard created with the REST API you will then want to select the boxes allowing for HTTP/HTTPS traffic. However if you are running directly in the command line, then you will not need to choose these options.

10. Keep the default selections for the other configuration settings for your instance.

11. Finally from the summary panel on the right when you're ready, choose Launch instance. This will take a few minutes to complete.

New we'll start adding our files

12. Once you have created your instance you'll then want to find it's IP Address or Public DNS. If you followed the above steps and were taken to your new instance you should see this on the summary screen for the instance. Otherwise go to https://console.aws.amazon.com/ec2/  and select instances, and finally your desired instance.

13. First we'll connect to our instance directly via RDP per above. Once you have connected directly via RDP we now will want to move our relevant files to the instance. There are multiple ways you could do this either usage of an online File Share (Dropbox/Sharepoint/etc), or alternatively uploading/downloading via an S3 Bucket

The files we'll need to move are

14. Once everything has been moved and you are connected to machine running is as simple as java -jar NAMEOFYOURJARHERE.jar. Of course if this is meant to be a long running process (aka not a batch style run, but something accessible via the web) you will want to use tools to keep the process running after your close your login session. For Windows you can use the javaw instead of java to maintain a long-running process.