Deployment of Litmus Edge Manager as an Azure Application
You can deploy Litmus Edge Manager as an Azure application.
The Azure application comes with a site license, which is automatically activated upon deployment and remains valid for five years. Tag consumption will be tracked and reported to Azure to ensure accurate billing.
The publisher, Litmus, maintains complete control over the virtual machine through a managed resource group, while the customer's access to the virtual machine is limited.
Important for Cloud Deployment: Before activating the license, ensure that all hardware or Virtual Machines (VM) configuration steps, such as adding or replacing a Network Interface Controller (NIC), are completed. Any changes to the VM hardware configuration may invalidate the licensing settings.
Select Create a resource.
In Search service and marketplace bar, enter Litmus.
From the list of services, select Litmus Edge Manager - Azure Application.
- Define the following:
- Resource Group: Define a resource group to deploy in
- Region: Define a region to deploy.
- Application Name: Define a name for the Litmus Edge Manager application.
- Managed Resource Group: Select Managed Resource Group.
- Click Review + Create.
- Agree to Terms & Conditions and fill in Contact Information on the next page.
Click Create.
- Check the inbound firewall rules in the virtual network once the application is deployed successfully:
- 443/tcp: LEM UI access
- 8446/tcp: LEM admin console UI access
- 8883/tcp: LE to LEM MQTT connection
- 51820/udp: LE to LEM remote access connection
- Depending on desired network and architecture, we can define specific ranges of IP for source and destinations.
- Review for all required and optional inbound/outbound Litmus Edge Manager Firewall Port Configuration Requirements.
- Navigate back to the Overview page.
- In the essentials section you will find the IP address associated to Litmus Edge Manager instance by Azure.
[Optional] Configure DNS
IP to access Litmus Edge Manager
Note: User access to UI will be determined by network & firewall configuration.