---
title: "System requirements for Zesty Disk on standalone instances"
slug: "system-requirements"
updated: 2026-03-12T13:46:47Z
published: 2026-03-12T13:46:47Z
canonical: "docs.zesty.co/system-requirements"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zesty.co/llms.txt
> Use this file to discover all available pages before exploring further.

# System requirements for Zesty Disk on standalone instances

- [Operating systems](/v1/docs/system-requirements#supported-operating-systems)
- [Managed services](/v1/docs/system-requirements#supported-managed-services)
- [Instance and volume settings](/v1/docs/system-requirements#required-instance-and-volume-settings)
- [Infrastructure](/v1/docs/system-requirements#required-infrastructure)

### Supported operating systems

Even if an operating system is not supported, you can automatically extend filesystems using the Zesty Disk Auto Extend feature. For more information, see [Automatically extend other filesystems](/v1/docs/automatically-extend-unsupported-filesystems-1).

| Operating system | Type | Release | Processor | Notes |
| --- | --- | --- | --- | --- |
| Linux (Btrfs) |  |  |  | - For all Linux types, use kernel versions 5.x and later. - A maximum of 4 Zesty Disk filesystems can be attached to an instance. |
|  | Amazon Linux | 2, 2023 | Intel, ARM-based |  |
|  | Red Hat Enterprise Linux (RHEL) | 8.10 | Intel |  |
|  | Rocky | 8.10 | Intel, ARM-based |  |
|  | SUSE Linux Enterprise Server (SLES) | 15 SP1, 15 SP3 |  |  |
|  | Ubuntu | 22.04, 24.04 | Intel, ARM-based |  |
| Linux (OpenZFS) |  |  |  | - For all Linux types, use kernel versions 5.x and later. - A maximum of 4 Zesty Disk filesystems can be attached to an instance. |
|  | Rocky | 9.*, 10.* | Intel, ARM-based | For v9.5, kernel version 5.14.0-503.14 is not supported. Release versions per request. |
|  | RHEL | 9.*, 10.* | Intel, ARM-based | Release versions per request |
| Windows |  |  |  |  |
|  | Windows Server | 2016-2025 | Intel | - A maximum of 2 Zesty Disk filesystems can be attached to an instance. |

The following filesystems and volumes are not supported:

- Root filesystems
- Boot or EFI volumes
- Volumes that are mounted with overlays, such as storage volumes or block devices of EKS/Kubernetes nodes

### Supported managed services

|  | Release |
| --- | --- |
| Amazon EMR | 5.3.10, 5.31.1, 5.36.1 6.3.1, 6.10.0, 6.11.0, 6.12.0, 6.13.0, 6.14.0, 6.15.0 7.0.0 to 7.10.0 (requires AL2023) |

### Required instance and volume settings

These settings are required for an AWS instance and EBS to be compatible with Zesty Disk.

| Setting | Requirements |
| --- | --- |
| Volume | - EBS volume that is not root. - **Minimum size**: Enough for 5-10 minutes of runtime (minimum 30 GB) **Tags** - **Tag key**: ZestyDisk - **Tag value**: True - **Resource type**: Volumes (not Instances) |
| Network settings | **Outbound security group** - Type = HTTPS - Destination = Anywhere-IPv4 (0.0.0.0/0 is the one that is needed, despite the AWS warning.) If you must provide a specific destination for outbound HTTPS traffic, the target URL is [https://api.cloudvisor.io](https://api.cloudvisor.io) |

### Required infrastructure

- Your VPC must have outbound access to the internet. If this is not possible, Zesty Disk supports secured connectivity using AWS PrivateLink. For more information, see [Enable PrivateLink for Zesty Disk](/v1/docs/enable-privatelink-for-zesty-disk).
- Zesty Disk requires minimal CPU resources to operate. You are required to maintain at least 3% of free CPU usage to allow the Zesty Disk agent to operate. If your CPU usage exceeds 97%, the Zesty Disk Agent may not perform.

If you have questions or need additional help, reach out to [Customer Support](https://zesty.co/contact-us/?support).