> 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/supported-infrastructure.md).

# Supported Infrastructure

## Supported Operating Systems

Datafy can be installed on the following Linux distributions:

<details>

<summary>Ubuntu</summary>

* 20.04
* 22.04
* 24.04

</details>

<details>

<summary>Amazon Linux</summary>

* AL2
* AL2023

</details>

<details>

<summary>Bottlerocket</summary>

* 10 latest versions

</details>

<details>

<summary>RHEL</summary>

* RHEL 8 - [latest version](https://access.redhat.com/articles/red-hat-enterprise-linux-release-dates#RHEL8)
* RHEL 9 - [latest version](https://access.redhat.com/articles/red-hat-enterprise-linux-release-dates#RHEL9)

{% hint style="info" %}
If you're running an older minor version contact Datafy support
{% endhint %}

</details>

{% hint style="info" %}
Don't see your OS version in the list? Let us know, we're always expanding our support!
{% endhint %}

## Supported Configurations

The following instance and volume configurations are supported for utilization reporting (Sensor and Autoscaler) and for autoscaling (AutoScaler).

<table><thead><tr><th width="198.9112548828125"></th><th align="center">Utilization Reporting</th><th align="center">Autoscaling</th></tr></thead><tbody><tr><td>Hypervisor</td><td align="center">All</td><td align="center"><a data-footnote-ref href="#user-content-fn-1">Nitro</a></td></tr><tr><td>Instance size</td><td align="center">All</td><td align="center">≥ <code>xlarge</code> recommended</td></tr><tr><td>Volume types</td><td align="center">All</td><td align="center">gp2, gp3</td></tr><tr><td>Volume size</td><td align="center">All</td><td align="center">from 20 GiB to 16 TiB</td></tr><tr><td>Boot volumes</td><td align="center"><span data-gb-custom-inline data-tag="emoji" data-code="2714">✔️</span></td><td align="center"><span data-gb-custom-inline data-tag="emoji" data-code="2716">✖️</span></td></tr><tr><td>LVM</td><td align="center">VGs with a single PV</td><td align="center"><span data-gb-custom-inline data-tag="emoji" data-code="2716">✖️</span></td></tr><tr><td>Multi-attach volumes</td><td align="center">Reported utilization may be incorrect</td><td align="center"><span data-gb-custom-inline data-tag="emoji" data-code="2716">✖️</span></td></tr><tr><td>Single- or Multi-partition volumes</td><td align="center">Reported utilization may be incorrect</td><td align="center"><span data-gb-custom-inline data-tag="emoji" data-code="2716">✖️</span></td></tr></tbody></table>

### Additional Considerations

{% hint style="info" %}
If your Kubernetes cluster contains a mix of supported and unsupported node types, see [Kubernetes Node Scheduling](/set-up-and-installation/advanced-setup/kubernetes-node-scheduling.md#partial-cluster-installation) to install AutoScaler only on the nodes that support it.
{% endhint %}

{% hint style="warning" %}
On EC2 instances, autoscaling will not be enabled for volumes that do not follow the [best practice](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-using-volumes.html) of using the filesystem UUID in the relevant `/etc/fstab` entry. Using the device path (e.g., `/dev/sdf` or `/dev/nvme1n1`) can result in failure to mount an autoscaling volume after reboot or mounting the volume to the wrong mountpoint, and is not supported.
{% endhint %}

[^1]: All new instance types use the Nitro hypervisor. See [AWS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#instance-hypervisor-type) for breakdown by instance type


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.datafy.io/set-up-and-installation/supported-infrastructure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.