How Do I Configure VLM on AWS for Client Access?

Updated Jul 6, 2026

Environment

Software

  • Volume License Manager

Other

  • Amazon Web Services (AWS)

This article explains how to configure an AWS-hosted Windows server running Volume License Manager (VLM) to allow client machines to connect successfully.

You will configure:

  • AWS security group inbound rules
  • Windows firewall settings on the server
  • Client-side host resolution

1. Configure AWS Security Group (Inbound Rules)

 

  • During AWS setup, you have to configure network access:

  1. In Network settings, click Edit.
  2. Enable: RDP (TCP 3389) → set source to Anywhere
  3. Create or select the security group.

 

  • After instance creation, update inbound rules. Add the following rules:

  1. TCP 3389 → RDP access
  2. TCP 27000 → License manager port
  3. TCP 4637 → Vendor daemon port
  4. Allow ICMP for connectivity testing.
  • Note: If you are using custom ports in your VLM, set accordingly. Port 27000 and 4637 are the default ports for VLM, FlexLM and many mult-iseat license management software. If you are running multiple servers, to avoid port conflict, it is recommended to change the default ports.

 

2. Install NI Volume License Manager

 

 

3. Configure Windows Firewall on the Server

 

  •  Enable ICMP (Ping)

  

  1. Open Windows Defender Firewall with Advanced Security
  2. Navigate to Inbound Rules
  3. Right-click: File and Printer Sharing (Echo Request - ICMPv4)
  4. Select Enable Rule
  5. Optional: You can also do it with Echo Request - ICMPv6

 

  • Allow VLM Executables

  1. Navigate to:
    Control Panel >> System and Security >> Windows Defender Firewall >> Allowed apps
  2. Click Allow another app…
  3. Add:
    • C:\Program Files (x86)\National Instruments\Shared\License Manager\Bin\lmgrd.exe
    • C:\Program Files (x86)\National Instruments\Shared\License Manager\Bin\nilm.exe

 

 

  • Enable Required Service

 

  1. In Allowed apps, ensure enabled:
    • Flexera
    • NI License Manager Daemon
  2. Enable for the required network profile (Private/Public).

 

 

4. Configure Client Hosts File

  1. On the client machine, open: C:\Windows\System32\drivers\etc\hosts 
  2. Run the editor as Administrator
  3. Add a new line: <SERVER_PUBLIC_IP> <SERVER_HOSTNAME> 
  4. Save the file.

After completing these steps:

  • The AWS-hosted VLM server is accessible over required ports
  • Windows firewall allows license communication
  • Client machines can resolve and connect to the server

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.