> For the complete documentation index, see [llms.txt](https://docs.datafy.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datafy.io/set-up-and-installation/datafy-installation/network-access.md).

# 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  | <p>76.223.36.164<br>13.248.178.22</p> |
| agent.datafy.io             | 443  | <p>76.223.36.164<br>13.248.178.22</p> |
| iac.datafy.io               | 443  | <p>76.223.36.164<br>13.248.178.22</p> |
| 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

{% hint style="success" %}
HTTPS proxy support is available from AutoScaler version 1.37.1 (Helm chart 3.5.1).
{% endhint %}

If your instances reach the internet through an HTTPS proxy, configure the following before or during [installation](/set-up-and-installation/datafy-installation/installation.md). 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.

{% tabs %}
{% tab title="EC2" %}
Define the proxy in environment variables before installing Datafy:

{% code overflow="wrap" %}

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

{% endcode %}

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

{% tab title="Helm" %}
Add the proxy values to your `helm upgrade --install` command:

{% code overflow="wrap" %}

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

{% endcode %}

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

{% hint style="info" %}
`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:

{% code overflow="wrap" %}

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

{% endcode %}
{% endhint %}
{% endtab %}
{% endtabs %}

{% hint style="info" %}
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.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.datafy.io/set-up-and-installation/datafy-installation/network-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.