Network Access

The Datafy agent makes outbound HTTPS calls to the endpoints below. No data from the instance is sent to Datafy, only the volume consumption statistics that power the management dashboard.

Endpoint URL	Port	Static IP Alternative
dso.datafy.io	443	76.223.36.164 13.248.178.22
agent.datafy.io	443	76.223.36.164 13.248.178.22
iac.datafy.io	443	76.223.36.164 13.248.178.22
ec2.<region>.amazonaws.com	443	—

The EC2 endpoint is regional. The agent calls the EC2 API in the region where it runs, so the simplest approach is to allow every region enabled on the AWS account.

Installing Behind an HTTPS Proxy

HTTPS proxy support is available from AutoScaler version 1.37.1 (Helm chart 3.5.1).

If your instances reach the internet through an HTTPS proxy, configure the following before or during installation. Datafy then routes all of its outbound traffic, including the calls to the endpoints above, through the proxy.

• HTTPS_PROXY (Helm: proxy.httpsProxy) — URL of the proxy server for the agent's outbound HTTPS traffic.

• NO_PROXY (Helm: proxy.noProxy) — comma-separated host, IP, CIDR, or DNS-suffix list to bypass the proxy. Include your environment's internal ranges so local traffic doesn't route through the proxy. Optional.

EC2

Define the proxy in environment variables before installing Datafy:

HTTPS_PROXY="http://10.0.0.5:3128"
NO_PROXY="10.0.0.0/8,.internal.example.com"

The installer writes the values to the agent's environment file and re-applies them on every upgrade.

Helm

Add the proxy values to your helm upgrade --install command:

--set proxy.httpsProxy="http://10.0.0.5:3128" \
--set proxy.noProxy="10.0.0.0/8\,.internal.example.com"

The chart renders the proxy variables on the AutoScaler DaemonSet, the controller, and the CSI proxy sidecar.

proxy.noProxy is passed through to the agent verbatim. Helm's --set splits values on commas, so each comma in the list must be escaped as \,. For longer bypass lists, pass the values through a file instead:

# values.yaml
proxy:
  httpsProxy: "http://10.0.0.5:3128"
  noProxy: "10.0.0.0/8,.internal.example.com"

The agent always bypasses 169.254.169.254 (the EC2 instance metadata endpoint), 127.0.0.1, and localhost. Anything passed in NO_PROXY is appended to that list.