Collector Requirements

The Machine with Collector Software installed acts as a server.

Before you install a Collector please consider that the machine with Collector Software is a server. It’s intended use is collecting data for the Insight Platform and it should not be used for any other purpose.

In order to set up a collector the following requirements should be met. If you do not meet these requirements before attempting to set up a collector it may not operate properly. Read the following sections and understand their importance to determine if deploying a collector is right for your organization.

General Requirements and Recommendations

Consider the following before choosing a Collector host:

  • DO NOT install a Collector on a host that already runs a Security Console or Scan Engine.
    • Security Consoles and Scan Engines will not function properly if a Collector is present on the same host.
  • Only install one Collector per machine, whether physical or virtual.
    • Additionally, Rapid7 recommends that the host be entirely dedicated to the Collector’s use to maximize resource availability.
  • Your Collector host must be configured with a Fully Qualified Domain Name (FQDN).

Hardware Requirements and Recommendations

You can install a Collector on a network server or virtual machine that meets the following minimum hardware requirements:

  • 2 CPU cores with 2GHz+ on each core
  • 8 GB RAM
  • 60 GB available disk space

For optimal performance, Rapid7 recommends the following hardware specifications:

Collector Size

Number of Agents

Recommended CPU Cores

Recommended RAM

Recommended Disk Space*


Up to 500


8 GB

60 GB


Up to 2,400


8 GB

80 GB


Up to 600 per CPU core**


16 GB

100 GB

* Disk Space

In cases where a connection to the Insight Platform is interrupted or lost, the Collector will hold data in the form of logs written to the disk until a connection can be reestablished.

The more disk space a Collector has, the longer it can operate without a connection to the Insight Platform.

** CPU Cores

The Collector can only be responsible for 600 agents per CPU core. Mutlicore CPUs are recommended for taking on additional agents per Collector.

If your Collector CPU usage stays consistently above 40% under normal load, consider deploying an additional Collector.

Supported Operating Systems

Your Collector host must run one of the following 64-bit operating systems:

  • Ubuntu 10.04 - 20.04
  • Debian 7.0 - 8.2
  • CentOS 5.2 - 7.3
  • Oracle Enterprise Linux (OEL) 5.2 - 7.3
  • Fedora 17 - 25
  • SUSE Linux Enterprise Server (SLES) 11 -12
  • SUSE Linux Enterprise Desktop (SLED) 11 -12
  • openSUSE LEAP (42.1 - 42.2)
  • Amazon Linux
  • Red Hat Enterprise Linux (RHEL) 5.2 - 7.3
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2008 R2
  • Windows 7 and newer

Supported Browsers

You need to access your InsightVM web interface in order to retrieve the installer and complete the activation process. To do so, use either of the following supported web browsers:

  • Mozilla Firefox (latest stable version)
  • Google Chrome (latest stable version)

Networking Requirements

Implementing Collectors for the InsightVM use case requires the following connectivity.

Collector communication with Insight Agents

Since InsightVM implements Collectors as intermediaries between your deployed Insight Agents and the Insight Platform, your Collectors must allow different kinds of traffic from your agents on the following ports:

Data TypeDirectionPort
Agent communication to CollectorInbound5508
Agent update requests to CollectorInbound6608
Agent file upload to CollectorInbound8037 (TCP and UDP)

Collector communication with the Insight Platform

Is your Rapid7 product subscription provisioned for the United States? Check your region code first!

As of April 12th, 2021, all new customers subscribing to Rapid7 Insight products that elect to store their data in the United States will be provisioned for one of three data centers. Since these data centers have unique endpoints, any firewall rules you configure must correspond to the data center your organization is assigned to. Follow these steps to determine which United States data center your organization is part of:

  1. Go to and sign in with your Insight account email address and password.
  2. Navigate to the Platform Home page.
    • If you are not taken to this page by default, expand the product dropdown in the upper left and click My Account.
  3. Look for the Data Storage Region tag in the upper right corner of the page below your account name. Your United States region tag will show one of the following data centers:
    • United States - 1
    • United States - 2
    • United States - 3

All Collectors must be able to establish outbound connectivity on port 443 to * and communicate with the domains shown in the Data and Storage (S3) columns of the following table according to your geographic region. For example, for InsightVM subscribers that elect to store their data in Australia, Collectors must be able to communicate with the following endpoints using port 443:

  • *
RegionData endpointStorage (S3 endpoint)
United States -
United States -
United States -

If you intend to deploy token-based Insight Agents through your Collectors, you also need to allow outbound connectivity from each Collector on port 443 to the endpoint that provides the agent's configuration files. Just like the Data and Storage endpoints in the previous table, you can configure your firewall rules to allow your Collectors to connect to a region-specific version of the Deployment endpoint to meet this requirement:

RegionDeployment endpoint
United States -
United States -
United States -

Collector communication for InsightVM-specific data

Finally, your Collectors must be able to reach out on port 443 and communicate with one of the following InsightVM-specific endpoints according to your geographic region. This endpoint is responsible for displaying your vulnerability assessment data and powers several InsightVM features:

United States -
United States -
United States -

Firewall rule alternatives

If you need an alternative to the URL firewall rule configuration method shown here, see the Insight Agent connectivity requirements page for a table of IP addresses by region that you can use instead.