The Zesty Disk Dashboard provides insights and analytics on your Amazon Elastic Block Store (EBS) usage, costs, and savings potential. It offers a detailed breakdown of account-specific EBS expenditures, type-based cost analysis, and over-time trends, making it easier to manage and optimize cloud storage expenses. All the data presented is based on a CUR that was uploaded to the Zesty platform. If no data is presented, no CUR has been uploaded yet. To create and then integrate a Zesty-compatible CUR, see Create a legacy CUR . Dashboard sections The following table describes the savings and cost analyses that you can make from the Zesty Disk Dashboard tab: Section Description Benefit Potential savings (A) Your organization’s estimated monthly savings by using Zesty Disk’s automation capabilities. This calculation is based on disk size adjustments and reducing over-provisioning costs. Potential savings is not relevant (not shown) for …

We can. Zesty has no insight into what our customers are doing with their instances. We only receive the usage metadata on running instances that is necessary for determining how best to cover them with commitments. Provided that your container workloads are backed by EC2, we can cover them with RIs.

EZswitch operates as a Kubernetes Custom Resource (CR) managed by a controller. It coordinates syncing jobs (using rsync under the hood), the final switchover to a Zesty-based StatefulSet (with the same properties as the initial STS), and supports both automatic or manual migration phases. Migration statuses (.status.status) After EZswitch starts, it follows these steps in completing the migration: InstallRequirements : Sets up necessary RBAC permissions and prerequisites. Init : Creates corresponding PVCs under the Zesty storage class. CreateSyncJobs : Launches sync jobs to copy data from the original PVCs to the new PVCs. Syncing : Continuously synchronizes data to ensure the new PVCs mirror the old ones in near real-time. ReadyForMigration : If autoMigrate=false, the migration pauses here until resumed with the migrate command or by setting autoMigrate=true on the EZswitch resource. If autoMigrate=true, the migration proceeds by scaling down the original StatefulSet. CreatingFinalSyncJobs : Sets up final sync jobs …

...

This topic describes how to deploy and configure Storage Autoscaling . Installation is based on a Helm chart published in github repo . Prerequisites A running EKS cluster, v1.7 or later, with the EBS CSI add-on installed, with one storage class defined Kubectl is installed Access to the Zesty platform For more information, see Access the Zesty platform The Zesty API key For more information, see Find your Zesty API key . Outbound HTTPS communication from cluster nodes The AWS account ID of the cluster on which Storage Autoscaling is being installed Before deploying, share this ID with a Zesty Customer Support representative. Note that this ID may be different than the one from the Management account (formerly known as Master Payer account). To install Storage Autoscaling : Add or update the Zesty repository to your Helm client: To add the repository: helm repo add zestyrepo https://zesty-co.github.io/zesty …

...

This topic describes how to manually extend a ZFS-based Zesty Disk filesystem. Manual actions may be reverted automatically by the Zesty Disk backend according to the Zesty Disk algorithm and the state of the filesystem. You can extend in the following ways: Extend an EBS volume that is already part of a Zesty Disk filesystem Add a new EBS volume to a Zesty Disk filesystem Extend a volume that is already part of a Zesty Disk filesystem This section describes how to manually extend a ZFS filesystem by extending a volume that is part of that filesystem. Prerequisites Login access to the Zesty platform Root CLI access to the instance, for example by using SSH Access to the AWS console with IAM permissions to modify an existing EBS volume Limitations To see the AWS requirements for modifying an EBS volume, see Requirements for Amazon EBS volume modifications . After modifying …

role . The AWS Quick create stack page is opened. In the AWS console, scroll down to the Capabilities section. Select I acknowledge that AWS CloudFormation might create IAM resources with custom names , then click Create stack . In the AWS console, the CloudFormation > Stacks page is displayed. The Events tab shows the different events taking place. When the process is done, the CREATE_COMPLETE status is displayed. Verify the integration: From the AWS console CloudFormation page, select the Outputs tab and copy the ARN value. If the ARN value is not displayed, refresh the table until it is. In the Zesty platform Verify Integration screen of the wizard, paste the entire ARN value (including arn: ) in the ROLE ARN field, then click Connect . Unless you have more accounts to connect, click No . Zesty takes a few moments to finalize the integration and prepare the new account. The Create new account wizard …

If you have already integrated your AWS account with Zesty, and you want to update the IAM permissions, use the procedure described in Integrate and onboard your AWS account with Zesty .

This topic describes the Zesty Disk process and how filesystem expanding and shrinking works. The Zesty Disk continual optimization process The following process takes place after Zesty Disk has been deployed: Zesty creates a virtual filesystem that consists of several small storage volumes. Since Zesty Disk leverages the native cloud provider block storage devices (AWS EBS), your native tools, procedures, and SLAs are unchanged, while you remain the owner of your data and the only one that has access to it. Zesty Disk continuously tracks usage metrics (capacity, IOPS, and read/write throughput) as well as instance and disk metadata (such as instance type, disk type, volume names) which are sent unidirectionally to the Zesty backend. The usage and metadata metrics are processed by an AI model that generates a behavioral profile on the instance filesystem. It uses this profile to predict the usage patterns and fluctuations of the filesystem …

EZswitch is a Kubernetes utility designed to simplify the migration of stateful workloads from non-scalable PVCs to Zesty Disk PVCs with auto-scaling capabilities. The tool manages the entire lifecycle of this storage transition—from initial synchronization to final switchover—while offering flexibility in how migrations are initiated and controlled. EZswitch's primary purpose is to leverage Zesty's auto-scaling storage solution ( Kompass Storage ). By migrating existing StatefulSets (STS) to Kompass Storage PersistentVolumeClaims (PVCs), your workloads gain the ability to automatically scale storage capacity as data usage grows or shrinks, eliminating the need for manual PVC resizing.

...

This topic describes the types of Auto Extend policies that you can create, the simulation shown during creation, and limitations. You can create policies of the following types: Simple : enables you to define these parameters: Threshold: The disk utilization percentage at which you want Zesty to take action. Configuration: By how much to increase the disk size. For example, whenever 80% disk utilization is detected (threshold), Zesty will increase the size by 75GB (configuration). Advanced : enables you to define more advanced parameters: Comfort zone: The desired disk utilization percentage, to which the system will extend. Risk zone: The utilization threshold that will trigger an extend action to return back to the defined comfort zone. Start: The minimum disk size from which this policy tier will apply. End: The maximum disk size to which the disk can be extended under the policy or specific policy tier. You can also use advanced …

This topic describes the CLI commands for Kompass Storage EZswitch. All EZswitch commands are invoked via the CLI plugin: kubectl zesty ezswitch [flags] The following tables describe the commands, flags, and descriptions. start Starts the migration process, installing EZswitch components (including the Helm chart if not already installed) and creating the EZswitch CR. By default, all ezswitch resources will be on the zesty-ezswitch namespace Flag Default Description --autoMigrate true Run process automatically to completion if true. --stsNamespace default Namespace of the original STS. --set key=value (none) Override Helm chart values during installation. --logLevel int 4 Set the log level of ezswitch-controller. --zestyStsName -zesty Name of the new Zesty-based STS. --helm-namespace zesty-ezswitch Namespace where ezswitch resources will be created Example : kubectl zesty ezswitch start myapp-sts --autoMigrate=false --helm-namespace=custom-namespace --set logLevel=4 migrate Resumes the migration if previously halted at ReadyForMigration. Flag …

A detailed summary of terms and definitions contained in the standard monthly Zesty bill and, where appropriate, how these numbers are calculated. If there is anything you find unclear, or you require further assistance in understanding your bill, reach out to your Customer Success Manager or open a support ticket . Detail TOTAL: The aggregate financial total of all actions detailed in subsequent sheets. Organization ID - the identification number of the organization the bill refers to. For customers with multiple organizations, you will receive a separate bill for each. Service - the specific product or service being billed. Potential Cost - the total standard on-demand equivalent cost of the EC2 instances used with no commitments applied. Actual Cost - the amount owed to AWS for EC2 usage after commitment based discounts have been applied. Saved - the difference between the potential cost and actual cost. Zesty Fee in % - the applicable fee for your business …

This topic describes the following minimum requirements and settings that are verified to work with Storage Autoscaling : Operating systems Instance settings Infrastructure Supported operating systems Operating system Type Release Processor Notes Linux Amazon Linux 2023 Intel, ARM-based Amazon Linux 1, 2 Intel, ARM-based Bottlerocket 1.24.x Intel, ARM-based EZswitch is not supported Required instance settings These network settings are required on all cluster nodes to be compatible with Storage Autoscaling . Setting Requirements 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 CPU and RAM resources to operate. For more details, see the Storage Autoscaling …

We do have a minimum threshold. At this time we require customers to have a minimum monthly on-demand EC2 spend of $7k.

This topic describes how to run EZswitch on a Linux instance from the zestyctl CLI. Before beginning EZswitch , ensure that your environment is supported, as described in the “Limitations” section of How EZswitch works on standalone instances . This topic describes the basics of how to use the zestyctl CLI to run EZswitch. For more options and a full description of the zestyctl disk ezswitch commands, see zestyctl disk ezswitch commands . Prerequisites User access to the Zesty platform and the Zesty API Key For more information, see Find your Zesty API key . AWS account is integrated with Zesty Disk For more information, see Integrate and onboard your AWS account with Zesty . A mounted volume (the source filesystem) with data to be migrated Root CLI access (for example, using SSH) to the instance with the source filesystem To run EZswitch from the zestyctl CLI: Connect to the instance with CLI root access …

Signing up for Zesty directly through the AWS Marketplace helps to keep all of your AWS-related expenses in one place, making it easier for finance teams to monitor and assess cloud spend and reducing the number of vendors they need to interact with directly each month. The Zesty fee will appear as a simple line item under the name Advanced Reserved Instance Automation for easy reference. If your business has an EDP set up with AWS, signing up through the Marketplace also ensures that your Zesty fee is counted towards your annual EDP commitment. One of our Account Executives can walk you through the process of setting this up during the sales process. A note on the billing cycle: Zesty runs billing on the 3rd of the month in order to get the most accurate data possible for the previous month's bill. AWS sends invoices out to their …

What is Storage Autoscaling ? Storage Autoscaling is an auto-scaling storage solution that dynamically manages Persistent Volumes (PVs) for Kubernetes workloads. It automatically adjusts the size of storage volumes based on actual usage, helping to reduce cloud storage costs and improve resource efficiency. What Kubernetes environments does Storage Autoscaling support? Storage Autoscaling supports Amazon EKS (Elastic Kubernetes Service). Which workloads does Storage Autoscaling support ? All workload types are supported. StatefulSet workloads are fully supported; others have beta support. How do I install Storage Autoscaling in my Kubernetes cluster? Storage Autoscaling is deployed using a Helm chart. For more information, see Deploy PVs Autoscaling . Storage Autoscaling will integrate with your existing Storage classes and begin managing them automatically. Existing PVCs will need to be migrated to work with Storage Autoscaling . What kind of applications benefit most from Storage Autoscaling ? The applications that benefit most are those that require dynamic storage management …