Deployment and networking requirements

Learn about the deployment architecture based on certificates for HTTPS connections and the associated port and DNS requirements.

Deployment

With this deployment model, all connections to PEG remain within networks that you control.

Architecture

In this architecture, you must create and manage the certificates for HTTPS connections

Port requirements

The following table lists the port requirements for ingress and egress IP addresses.


Port	Protocol	Purpose	Ingress private IP	Egress to public internet
22	TCP	ssh connectivity for Admin	✓
443	TCP	Ingress Desktop sensor and business analyst connectivity over HTTPS (TLS 1.2) Egress PEG sends redacted data to Process Discovery. Also used to pull down PEG installer, updates, and so on from our repositories Sensor connects directly to Process Discovery cloud to get configuration information only. No collected data is sent directly from the sensor to the Process Discovery cloud.	✓	✓
80	TCP	Used for redirection from http to HTTPS (443)	✓

DNS requirements

You will provide PEG with an apex domain name that you want to use (for example, example.com). Based on that, PEG will inform you about the DNS sub domain records that you must create.

Automation 360