Planning Endpoint Agent Manager deployment
Requirements
Service connectivity requirements are shown below. The table is provided with default port values and they could be changed at installation time:
Source | Destination | Port | Protocol | Comments |
---|---|---|---|---|
EA Manager | Devo Entrypoint | 443 | TCP | Devo Platform log upload |
EA Manager | Devo Relay | 13000 | TCP | Only for deployments using a relay instead of direct connection to Devo platform |
EA Manager | MySQL | 3306 | TCP | EA Manager MySQL backing store |
EA Manager | 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 |
Python must be previously installed on all manager hosts. See here for more information.
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. Another type of 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.
Minimal 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 to 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
1 REDIS
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, then they will stop processing, leaving the file descriptors open. This will cause the server to become overwhelmed and unresponsive. Therefore, deploying on T instances is not recommended.
Requirements can change due to a number of factors depending on your deployment scenario. Please contact Devo for a more accurate estimate of the sizing for a particular customer environment.
Supported versions of OS for Endpoint Agent Manager
Other OS versions may actually work but have not been specifically tested by the development team.
RHEL 7 and 8
Ubuntu 20 and 22
Alma Linux 8 and 9
Amazon Linux 2
Contact Devo to get a deployment package for the Endpoint Agent.