Topics Discussed

Resource Requirements

RequirementWindows InstanceLinux Instance
CPU2 Cores1 Core
Disk Space3GB3GB
BandwidthEstimated 50-100Kb per minute, based on the logs generated in your system.

*Minimum required for installation. VMs might require more memory per your installation configuration.

TLS 1.2 is required to install the Armor Anywhere Agent 3.0. 
For more information on TLS 1.2, please visit Microsoft's documentation

Operating System Compatibility

Operating System

Supported Version for 64-bit Environments Only

  • 7.X
  • 8.X

Red Hat Enterprise Linux (RHEL)

  • 6.X
  • 7.X
  • 8.X
  • 16.04
  • 18.04
  • 20
Amazon Linux
  • 2015.03
  • 2015.09
  • 2016.03
  • 2016.09
  • 2017.03
  • 2017.09
  • 2018.03
  • Amazon Linux 2
Oracle Linux
  • 6.X
  • 7.X
SUSE Linux Enterprise Server
  • 12
  • 15
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019

For Windows users, PowerShell 3 must be installed.

For Windows 2012 users, when you install the Armor Agent, the corresponding Trend Micro agent will require a reboot. 

  • 9
  • 10 (anticipated for production April 30)

For Windows users, in order to run the install script, you will need to ensure your execution policy allows for the execution of scripts.

  • You can check by executing the following command in Powershell
Get-ExecutionPolicy -List
  • If the ExecutionPolicy is set to AllSigned or RemoteSigned for LocalMachine, let's UnBlock it for the script installation by adding the UnBlock command to the installation one-liner
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Invoke-WebRequest -outfile armor_agent.ps1 ; Unblock-File -Path .\armor_agent.ps1 ; .\armor_agent.ps1 -license 1AAAA-AAAAA-AAAAA-AAAAA-AAAAA -region us-west

Browser Support

The Armor Management Portal (AMP) supports the current version of the following browsers:

  • Chrome
  • Firefox
  • Internet Explorer
  • Safari

 Armor cannot guarantee that previous versions will be supported.

Firewall Rules

This topic only applies to Armor Anywhere users.

The following ports will need to be opened for each server registered with Armor.

Armor Anywhere Agent Services





OutboundArmor Agent
  • 443/tcp
    • (
OutboundMalware Protection, FIM, IDS
  • 4119/tcp
  • 4120/tcp
  • 4122/tcp

 Rackspace Users
  • 443/tcp
  • 4120/tcp
  • 4122/tcp

 Rackspace Users
    • ([region]
OutboundVulnerability Scanning
  • 443/tcp
    • (
OutboundLog Management (Filebeat / Winlogbeat)
  • 5516/tcp
    • (

For Log Relay, the following additional ports will need to be opened for each server registered with Armor.

Log Relay Services





InboundLog Relay (Logstash)
  • 5140/udp
  • 5141/tcp
  • The IP address for your virtual machine
OutboundLog Relay (Armor's logging service (ELK))
  • 5443/tcp
  • 5400-5600/tcp (Reserved)

    Armor reserves the right to utilize this port range for future expansion or service changes.

After you install the agent, Armor recommends that you test the connection for each configured firewall rule.

To verify connectivity to an Armor service endpoint, use the telnet command.

The following example tests connectivity to over 443/tcp:

telnet 443

For Windows systems without the telnet feature installed, you can also use PowerShell:

new-object System.Net.Sockets.TcpClient('', 443)

Remove Anti-Virus Software

If you intend to use the Anti-Virus module, you must remove any previously installed anti-virus software, such as Trend Micro, McAfee, etc. Afterwards, you must reboot your system. 

Related Documentation

Additional Documentation for Installing Armor Anywhere with secure hosting

Was this helpful?
Your Rating: Results: 1 Star2 Star3 Star4 Star5 Star 20 rates