Document toolboxDocument toolbox

Endpoint Agent Manager deployment

Owned by Juan Tomás Alonso Nieto (Deactivated)
May 23, 2022
2 min read
[ 1 Prerequisites ] [ 2 Endpoint Agent Manager deployment ]

Prerequisites

  • Service connectivity requirements (the following table is provided with default port values and they can be changed at installation time):

Source

Destination

Port

Protocol

Comments

Source

Destination

Port

Protocol

Comments

EA Manager

Devo Entrypoint

443

TCP

Devo Platform log upload.

Devo Relay

13000

TCP

Only for deployments using a relay instead of direct connection to Devo platform.

MySQL

3306

TCP

EA Manager MySQL backing store.

REDIS

6379

TCP

EA Manager REDIS cache.

Endpoint Agent / Load Balancer*

EA Manager / Load Balancer*

8080

TCP

EA Manager log upload.

Endpoint Agent / MDM Server / Download Server / Load Balancer*

EA Manager / Load Balancer*

8081

TCP

Endpoint Agent repository. The agent can be downloaded from a different computer and distributed by your usual MDM tooling to the endpoints.

Operations laptops

EA Manager / Load Balancer*

8080

TCP

Web UI access to EA Manager.

*For distributed deployments where there is more than one EA Manager in place, make sure that flows are enabled via your preferred Load Balancer.

  • The table above depicts the connectivity required for the platform to be in service. Other connectivity might be required for deployment as the deployment tools make use of external dependencies. As a general prerequisite, the EA Manager server should have outbound internet access. If that is not possible, check here for a comprehensive list of required outbound connectivity during the deployment phase.

  • Minimum configuration requirements:

    • 1 Server/VM 2 CPUs x 4GB RAM for Endpoint Agent Manager.

    • Endpoint Agent Manager will deploy a dockerized version of MySQL and REDIS on the same server.

For AWS deployments, it is recommended that you have more than 100GB volume size to ensure 300 IOPS capacity.

  • Standard configuration requirements:

    • 1 Server/VM 4 CPUs x 8GB RAM for Endpoint Agent Manager.

    • 1 MySQL cluster

    • 1 REDIS cluster

If you are deploying on AWS on T-type instances, there are different scenarios where the activity can increase and the instances will burst. If they run out of credits, they will stop processing, leaving the file descriptors open. This will cause the server to become overwhelmed and unresponsive. Therefore, deploying on T-type instances is not recommended.

Prerequisites can change due to a number of factors depending on your deployment scenario. Contact Devo for a more accurate estimate of the sizing for a particular customer environment.

Endpoint Agent Manager deployment

Installations of the Endpoint Agent Manager are specific for each customer or environment and, as a result, particular tokens and certificates are generated during the process. Contact the Endpoint Agent team to get assistance for the initial setup of the solution in a new environment until the final repositories and instructions are defined.

The following steps will help you set up an independent Endpoint Agent Manager environment for familiarization with the installation process, end-to-end testing, and so forth. 

Supported versions of OS for Endpoint Agent Manager. Not that other versions may work but have not been tested by the development team:

  • CentOS 7

  • RHEL 7 and 8

  • Ubuntu 18 and 20

  • Debian 9 and 10

CentOS 8 has been declared "End Of Life" on December 31st, 2021. As a result of that, official repositories stopped working on January 31st and deployment playbooks in Centos 8 will not work as expected. Deployment of Endpoint Agent Manager in Centos 8 will not be supported. See the official announcement here.

Contact Devo to get a deployment package for the Endpoint Agent.