Deploying Aqtra Platform from Azure Marketplace

For installation of the Aqtra Platform for Azure you need to use an image of a virtual machine accessible from Azure Marketplace. During your first installation you will need to use the default "servadmin" account with automatically generated password. This password you can find at virtual machine terminal or inside the "/root/sp_pwd" file.

After a successful installation, there will be two main areas available to you inside Aqtra Platform – Studio and Workplace.

Aqtra Studio is a tool you will use to configure your low-code applications. It is available at "http://IP-address/studio", where IP-address, that public IP of your virtual machine instance or it’s DNS domain name. For example: "http://192.168.0.1/studio/" or "http://test.aqtra.io/studio/".

Aqtra Workplace is where you and your users will access the applications you’ve developed.

It will be available at "http://IP-address". For example: "http://192.168.0.1" or "http://test.aqtra.io".

If you want to change your application domain name, you need connect with ssh to the virtual machine, where the platform is installed. (For your convenience we recommend using a tool like "Putty" or similar.). Then you’ll need to run command "sudo aqtra-platform set_domain test.aqtra.io" using terminal access (change to your domain name before executing the command).

To start working with Aqtra Platform Studio, you need use account "servadmin" with auto-generated password accessed as described above. If you ever need to reset this password outside Aqtra Studio, you must first connect using ssh to the virtual machine where the platform is installed. Then you’ll need to run "sudo aqtra-platform reset_password" command using terminal client.

Setting up Azure Firewall

Once you’ve set up your Aqtra Platform instance, you’ll need to also setup Azure Firewall service to make sure your instance of Aqtra Platform is working correctly.

For this, you need to access virtual machine settings in Azure, and go to tab Networking. Then you need to press Add inbound port rule button, and add the following rules:

• Source – “Any”, Inbound ports range – “*”, Destination – “Any””, Outbound ports range – “8080”, Name – “HTTP”, Protocol – “TCP”, Action – “Allow”, Priority - 310
• Source – “Any”, Inbound ports range – “*”, Destination – “Any””, Outbound ports range – “443”, Name – “HTTPS”, Protocol – “TCP”, Action – “Allow”, Priority - 320
• Source – “Any”, Inbound ports range – “*”, Destination – “Any””, Outbound ports range – “8081”, Name – “Custom”, Protocol – “TCP”, Action – “Allow”, Priority - 330
• Source – “Any”, Inbound ports range – “*”, Destination – “Any””, Outbound ports range – “5001”, Name – “Custom”, Protocol – “TCP”, Action – “Allow”, Priority - 340

Then you’ll need to do the same for the Outbound port rules:

• Source – “Any”, Inbound ports range – “*”, Destination – “Any””, Outbound ports range – “8080”, Name – “HTTP”, Protocol – “TCP”, Action – “Allow”, Priority - 100
• Source – “Any”, Inbound ports range – “*”, Destination – “Any””, Outbound ports range – “443”, Name – “HTTPS”, Protocol – “TCP”, Action – “Allow”, Priority - 110
• Source – “Any”, Inbound ports range – “*”, Destination – “Any””, Outbound ports range – “8081”, Name – “Custom”, Protocol – “TCP”, Action – “Allow”, Priority - 120