System requirements for Zesty Disk on standalone instances
  • 1 Minute to read
  • PDF

System requirements for Zesty Disk on standalone instances

  • PDF

Article summary

This topic describes the following minimum requirements and settings that are verified to work with Zesty Disk:

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.

Supported operating systems

Operating system

Type

Release

Processor

Notes

Linux

  • 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

2023

Intel, ARM-based

Amazon Linux

1, 2

Intel

Debian

12

Intel, ARM-based

Oracle Linux

7.8, 7.9

Intel, ARM-based

Red Hat Enterprise Linux (RHEL)

7.x, 8.x, 9.x

Intel

Rocky

9.3, 9.4

Intel, ARM-based

SUSE Linux Enterprise Server (SLES)

15 SP1, 15 SP3

Ubuntu

16.04, 18.04, 20.04, 22.04, 24.04

Intel, ARM-based

Windows

Windows Server

2016, 2019, 2022

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

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.)

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.

  • 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 any questions or need additional help, reach out to Customer Support.


Was this article helpful?