Edge Delta System Requirements

software and hardware requirements.

2 minute read

Operating System Compatibility

Operating System	Architecture	Distributions
Windows	x86_64 x86	Windows Server 2019
Linux	arm64 x86_64	Amazon Linux 2 Centos 8 Centos 7 Debian 10 (Buster) Debian 9 (Stretch) Nixos Ubuntu Raspbian
macOS(Darwin)	arm64 x86_64	Not applicable
Kubernetes	Not applicable, see here.	v1.14.X and later
Docker	arm64 amd64 Windows	Not applicable

Resource Requirements

Operating System	Architecture
CPU	0.2 core
RAM	256 MB

Browser Support

The Edge Delta App supports the current version of the following browsers:

Chrome
Firefox
Edge

There are reported compatibility issues with Safari. We do not recommend that you use a mobile device to access the Edge Delta App.

Firewall Rules

To successfully integrate with Edge Delta, you may need to update your network policies for outgoing access.

While the Edge Delta fleet can be deployed in restricted network environments where outgoing network traffic to the internet is strictly moderated, you must update network policies to enable outgoing access to these destinations and to bypass HTTP/HTTPS proxies.

Traffic	Port	Destination URI	Service
Outbound	443	`http://api.edgedelta.com`	Access the Edge Delta backend.
Outbound	443	53f55016dbcb4e5f8b7fdf4a14a4cacc.us-west-2.aws.found.io	Agent health status data and cluster patterns.
Outbound	443	Access the following link to view a list of IP ranges: https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html The following regions and services need to be unlocked: S3 us-east-1 S3 us-west-2 Use the following examples to retrieve the service URIs. `curl https://ip-ranges.amazonaws.com/ip-ranges.json \| jq -r ‘.prefixes[] \| select(.region==“us-east-1”) \| select(.service==“S3”) \| .ip_prefix’` `curl https://ip-ranges.amazonaws.com/ip-ranges.json \| jq -r ‘.prefixes[] \| select(.region==“us-west-2”) \| select(.service==“S3”) \| .ip_prefix’`	Metrics and Log Archiving.
Outbound	443	`https://app.edgedelta.com/saml` `https://api.edgedelta.com/saml/metadata` `https://api.edgedelta.com/saml/acs`	SSO on-premises.

In addition, configure one of the following rule sets:

Basic

For a basic configuration with a more permissive range of endpoints, configure this rule in addition to the preceding rules:

Traffic	Port	Destination URI	Service
Outbound	443	*.s3.us-west-2.amazonaws.com	Agent Profiling and Health.

Advanced

For a more advanced configuration with specific endpoints, configure these rules in addition to the preceding rules:

Traffic	Port	Destination URI	Service
Outbound	443	ed-agent-health.s3.us-west-2.amazonaws.com	Stores Agent Health
Outbound	443	ed-customer-contexts.s3.us-west-2.amazonaws.com	Stores Anomaly Captures
Outbound	443	ed-customer-archive-logs.s3.us-west-2.amazonaws.com	Stores Log archive
Outbound	443	ed-metrics.s3.us-west-2.amazonaws.com	Stores Metrics
Outbound	443	ed-data-hub.s3.us-west-2.amazonaws.com	Stores General Data

In an effort to provide security during fleet installation, starting with version 0.1.20 of the agents, the makeself –sha256 option will be included and enabled in all Fleet deployments. Specifically, makeself will perform md5 and crc checks for content integrity.