Document toolboxDocument toolbox

Planning Devo Relay deployment

Owned by Juan Tomás Alonso Nieto (Deactivated)
Last updated: Jun 13, 2024
3 min read
[ 1 Requirements ] [ 2 Deployment topologies ] [ 3 Compatibility between Devo Relay and Devo platform deployments ]

Requirements

Before starting with the relay installation, make sure you can provide a machine with the following requirements:

Note that you must prepare your network to reach the relay packages URLs specified below.

Hardware

Minimum requirements

  • 2 vCPU

  • Memory → 8 GB

  • Hard disk → The hard disk memory should be x2.25 the required disk buffer.

Storage requirements

Note that your required storage should be calculated in relation to the data ingest. Higher volumes of data would allow you to handle potential long downtimes in the network better.

Learn more about this in Relay buffers.

Software

Supported Operating Systems

  • Ubuntu 20 & 22

  • RHEL / CentOS 8 & 9

Note that Devo Relay up to version 2.5.0 was certified in Ubuntu 18 and RHEL / CentOS 7.x. These OSs will be unsupported by June 2024, so please upgrade your system to the newest versions.

Network

Ensure that the relay can access the following resources:

For US users

  • Devo ELB - (protocol: Syslog over TCP+TLS, endpoint: collector-us.devo.io, port: 443)

  • Relay API - (protocol: HTTPS, endpoint: api-us.devo.com, port: 443)

  • Query API - (protocol: HTTPS, endpoint: apiv2-us.devo.com, port: 443)

For US3 users

  • Devo ELB - (protocol: Syslog over TCP+TLS, endpoint: collector-us3.devo.io, port: 443)

  • Relay API - (protocol: HTTPS, endpoint: api-us3.devo.com, port: 443)

  • Query API - (protocol: HTTPS, endpoint: apiv2-us3.devo.com, port: 443)

For EU users

  • Devo ELB - (protocol: Syslog over TCP+TLS, endpoint: collector-eu.devo.io, port: 443)

  • Relay API - (protocol: HTTPS, endpoint: api-eu.devo.com, port: 443)

  • Query API - (protocol: HTTPS, endpoint: apiv2-eu.devo.com, port: 443)

For CA users

  • Devo ELB - (protocol: Syslog over TCP+TLS, endpoint: collector-ca.devo.io, port: 443)

  • Relay API - (protocol: HTTPS, endpoint: api-ca.devo.com, port: 443)

  • Query API - (protocol: HTTPS, endpoint: apiv2-ca.devo.com, port: 443)

For APAC (Asia-Pacific) users

  • Devo ELB - (protocol: Syslog over TCP+TLS, endpoint: collector-ap.devo.io, port: 443)

  • Relay API - (protocol: HTTPS, endpoint: api-apac.devo.com, port: 443)

  • Query API - (protocol: HTTPS, endpoint: apiv2-apac.devo.com, port: 443)

For GCP (Spain) users

  • Devo ELB - (protocol: Syslog over TCP+TLS, endpoint: collector-sasr.devo.io, port: 443)

  • Relay API - (protocol: HTTPS, endpoint: api-sasr.devo.com, port: 443)

  • Query API - (protocol: HTTPS, endpoint: apiv2-sasr.devo.com, port: 443)

These are the ports used by the relay:

  • Internal relay ports → 12996-12998

  • Reserved inbound ports → 12999 to 13002 configured with default rules

  • Custom inbound ports → 13003 to 13XXX reserved for custom rules (the exact number of ports depends on the number of rules to be created)

These ports should not be used by any other services.

Deployment topologies

Devo Relay can be deployed as a single node or in a cluster for High Availability (HA).

Single node requirements

  • One machine with the requirements listed above

  • One IP address for the relay

HA active-passive with 2 nodes

  • Two machines with the requirements listed above in the same network

  • 3 IP addresses (one per node and one for the virtual IP)

Compatibility between Devo Relay and Devo platform deployments

We strongly recommend using Devo Relay v2.X.X if you are using Devo with platform version 7.1.X or above.

Devo Relay version

Devo platform version

Devo Relay version

Devo platform version

1.4.2 and older

Any

2.X.X

7.1.X or above

You can check your Devo environment platform version by clicking Help → Customer support from the Devo navigation pane. The platform version appears at the left bottom corner of the window.

Â