ESET PRIVATE Scanning Solution – Table of Contents

System Requirements

Minimum system requirements for On-Premises or Private Cloud Deployment (AWS, Azure, GCP):

Operating system: Linux

Minimum Kernel Version: 5.4

Tested Distributions:

oUbuntu Server 22.04 or higher

oDebian 11 or higher

o Red Hat Enterprise Linux 9 or higher

CPU Architecture: AMD64 (x86-64) and ARM64 (both supported)

Multi-core Processor: Recommended

Storage: approximately 2GB per container

CPU Allocation Guidelines

For optimal performance:

Dedicate at least 1 CPU core to the Load Balancer container

Allocate remaining cores equally to Scanner containers

Example: On 8-core CPU → 1 core (Load Balancer) + 7 cores (7 Scanner containers)

Optional: +1 core for Configuration EngineAgent (telemetry/health monitoring)

In general, it is recommended to allocate one CPU core per component. The Scanner component effectively utilizes up to 1vCPU, additional cores provide no benefit. For higher throughput, spawn additional Scanner replicas.

Network Requirements (On-premises Deployments Only)

Network connection between the Load Balancer and Scanner (if they are not deployed within the same cluster).

Network connection between the Agent and Load Balancer (with sufficient throughput for scan files).

ESET Update Servers outbound connectivity from Scanner(s) for module updates.

Image Repository, Network access to the image repository at https://ecscn.azurecr.io/ for retrieving the latest Docker images of the ESET PRIVATE Static Scanning Engine components.

Private Cloud platform specifics: Refer to dedicated EKS/ECS sections.