System and network requirements

Verify that your system and network meet the minimum requirements before you install a DigiCert® agent.

The agent must be installed on the same system as the automated TLS/SSL certificates.

System requirements

The DigiCert agent software runs on Windows and Linux servers with the following requirements:

Server type	Supported OS versions	Minimum specifications
Windows	Windows 10 Windows Server 2016 Windows Server 2019 Windows Server 2022	64-bit OS version 2 GB RAM (4 GB recommended) 2 GB free disk space (minimum) Microsoft .NET Framework 4.x installed Administrator privileges
Linux	Red Hat Enterprise Linux 7.x Red Hat Enterprise Linux 8.x Red Hat Enterprise Linux 9.x Ubuntu 20.04 or later	64-bit OS version and US locale required 2 GB RAM (4 GB recommended) 2 GB free disk space (minimum) CLI utilities `awk`, `grep`, `sed`, `lsof`, and `dos2unix` installed Root privileges

Network requirements

The DigiCert agent on each host must be able to resolve the fully qualified domain names (FQDNs) for the local web server, either via DNS or a local "hosts" file.

To connect to Trust Lifecycle Manager, the agent requires outbound to the two DigiCert platform URLs in one of the following regions:

Region	Platform URLs¹	TCP port	Protocol
Americas (U.S.A.)	`one.digicert.com`, `clientauth.one.digicert.com`	443	HTTPS
APJ (Japan)	`one.digicert.co.jp`, `clientauth.one.digicert.co.jp`	443	HTTPS
EMEA (Netherlands)	`one.nl.digicert.com`, `clientauth.one.nl.digicert.com`	443	HTTPS
EMEA (Switzerland)	`one.ch.digicert.com`, `clientauth.one.ch.digicert.com`	443	HTTPS
_{1. For users with an on-premises DigiCert ONE deployment, the agent needs to access port 443 (HTTPS) on the local DigiCert ONE instance and ClientAuth host (for example, my-org.one.digicert.com and my-org.clientauth.digicert.com).}

In addition, the agent requires outbound access to the below host for Trust Lifecycle Manager discovery and automation services:

Region	URL	TCP port	Protocol
All regions	`automation-service.digicert.com` ¹	443	HTTPS
_{1. This service is delivered through a content distribution network (CDN) and the IP addresses may vary by region. If your organization uses IP-based allowlists, look up the automation-service.digicert.com host in your local region to determine which IP addresses to allow.}

Notice

If using a local DigiCert® sensor as proxy, the agent must also be able to connect outbound to the proxy listening port on the sensor. To learn more, see Use a sensor as a proxy server.

What's next

To install an agent on a single server, see: Install and activate a DigiCert agent.
To bulk install agents on multiple servers at once, see: Install DigiCert agents in silent mode.
If your organization has a private on-premises instance of DigiCert ONE, make sure you meet the additional requirements to use DigiCert agents for certificate lifecycle automation.

In this section: