Tech Writer Resources
Topics Discussed
Resource Requirements
| Requirement | Windows Instance | Linux Instance |
|---|---|---|
| CPU | 2 Cores | 1 Core |
| RAM | 2GB | 1GB |
| Disk Space | 3GB | 3GB |
| Bandwidth | Estimated 50-100Kb per minute, based on the logs generated in your system. | |
Operating System Compatibility
Operating System | Supported Version for 64-bit Environments Only |
|---|---|
| CentOS |
To use a Linux-based Armor Anywhere agent, you must have Python 2.7 installed. |
Red Hat Enterprise Linux (RHEL) |
To use a Linux-based Armor Anywhere agent, you must have Python 2.7 installed. |
| Ubuntu |
To use a Linux-based Armor Anywhere agent, you must have Python 2.7 installed. |
| Amazon Linux |
To use a Linux-based Armor Anywhere agent, you must have Python 2.7 installed. |
| Oracle Linux |
To use a Linux-based Armor Anywhere agent, you must have Python 2.7 installed. |
| Windows |
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. |
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 Anywhere.
Inbound / Outbound | Service / Purpose | Port | Destination |
|---|---|---|---|
| Outbound | Armor Agent | 443/tcp |
|
| Outbound | Malware Protection, FIM, IDS |
|
|
| Outbound | Log Management (Filebeat / Winlogbeat) | 515/tcp |
|
| Outbound | Monitoring | 8443/tcp |
|
| Outbound | Remote Access | 443/tcp |
|
| Outbound | Vulnerability Scanning | *443/tcp |
|
| Inbound | Log Relay (Logstash) |
| The IP address for your virtual machine |
| Outbound | Log Relay (Armor's logging service (ELK)) |
|
|
The agent will perform a lookup to the applicable DNS entry, which may resolve to one of multiple Amazon Web Services based subnets. As a result, if your firewall does not support outbound filtering by domain name, then you may need to open all outbound traffic to 443/tcp to accommodate this service.
Additionally, verify that your proxy server can externally communicate.
If your network environment's servers are behind specific firewall controls that block regular outbound communication, then you may want to perform a port-forwarding server deployment. To learn more, see Port-Forwarding and Proxy Server and Client Deployment.
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 api.armor.com over 443/tcp:
telnet 75.2.84.73 443
For Windows systems without the telnet feature installed, you can also use PowerShell:
new-object System.Net.Sockets.TcpClient('75.2.84.73', 443)
Remove Anti-Virus Software
Before you install the Armor Anywhere agent, you must remove any previously installed anti-virus software, such as Trend Micro, McAfee, etc. Afterwards, you must reboot your system.
Pre-Installation Scripts
Before you install the Anywhere agent, you can run the following scrips to verify that your environment is compatible.
Operating system | Script |
|---|---|
| sudo curl -sSL https://get.core.armor.com/latest/armor_agent.sh | sudo bash /dev/stdin |
| [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Invoke-WebRequest https://get.core.armor.com/latest/armor_agent.ps1 -outfile armor_agent.ps1 ; .\armor_agent.ps1 |
Related Documentation
Was this helpful?
| Your Rating: |
|
Results: |
|
14 | rates |
This page has no comments.