76.223.36.164
13.248.178.22
76.223.36.164
13.248.178.22
76.223.36.164
13.248.178.22
| Utilization Reporting | Autoscaling | |
|---|---|---|
| Hypervisor | All | Nitro |
| Instance size | All | ≥ xlarge recommended |
| Volume types | All | gp2, gp3 |
| Volume size | All | from 20 GiB to 16 TiB |
| Boot volumes | ✔️ | ✖️ |
| LVM | VGs with a single PV | ✖️ |
| Multi-attach volumes | Reported utilization may be incorrect | ✖️ |
| Single- or Multi-partition volumes | Reported utilization may be incorrect | ✖️ |
| Where | Mode | What you need |
|---|---|---|
| EC2 | Tokenless | An IAM instance profile attached to the instance, with IMDS access |
| EKS | IRSA | A dedicated IAM role for the controller's ServiceAccount, trusted by the cluster's OIDC provider |
| EKS | Node instance profile | IMDS access with a metadata hop limit of 2 or greater |
| Name | Description | Default | Range |
|---|---|---|---|
| Autoscaling Size Factor | When autoscaling is activated, the initial managed volume size will be at least this factor multiplied by the current used data. A higher value means more free space after activation. | 1.3 | 1.1 – 2.0 |
| Autoscaling Minimum Size (GiB) | The smallest absolute size an autoscaling volume can reach following initial activation. Even if actual usage is lower, the volume will not be sized below this value. Volumes with original sizes smaller than this cannot be autoscaled. | 50 GiB | 20 – 16,384 GiB |
| Autoscaling Minimum Size (%) | The smallest size an autoscaling volume can reach following initial activation, as a percentage of the original volume size. Works alongside the absolute minimum, whichever produces a larger size applies. | 10% | 5 – 100% |
| Autoscaling Maximum Size (GiB) | The maximum original volume size eligible for autoscaling. Volumes larger than this will not be autoscaled. | 16,384 GiB | Up to 16,384 GiB |
| Name | Description | Default | Range |
|---|---|---|---|
| Grow Factor | When a grow is triggered, the new volume size will be this factor multiplied by the current size. Higher values add more headroom per grow but temporarily use more storage. | 1.5 | Min 1.1 |
| Grow Minimum Free Space | An absolute free-space floor. Growth is triggered when free space on the volume drops below this value. Acts as a safety net to ensure volumes don't run out of space. | 5 GiB | Min 5 GiB |
| Name | Description | Default | Range |
|---|---|---|---|
| Shrink Threshold (%) | If not in shrink cooldown (see below), a shrink is triggered when the volume's utilization falls below this percentage (of the volume's current size). For example, at 50%, a volume using only 30 GiB out of a current size of 65 GiB will shrink. | 50% | 0 – 75% |
| Shrink Abort Threshold (%) | If a shrink is already in progress and the expected utilization in the new smaller size rises above this percentage, the shrink is aborted. | 85% | 80 – 100% |
| Shrink Size Factor | When shrinking, the new volume size will be at least this factor multiplied by the current used data, ensuring headroom remains after the operation. | 1.3 | Min 1.1 |
| Shrink Minimum Size (GiB) | The smallest absolute size a volume can be shrunk to. Even if actual usage is lower, the volume will not be sized below this value. | 50 GiB | 20 – 16,384 GiB |
| Shrink Minimum Size (%) | The smallest size a volume can be shrunk to, as a percentage of the original volume size. Works alongside the absolute minimum, whichever produces a larger size applies. | 10% | 5 – 100% |
| Shrink Cooldown Time | Minimum wait time after any autoscaling operation (activation, grow, or shrink) before a new shrink can be triggered. Prevents rapid grow/shrink cycling on volumes with fluctuating usage. | 60 min | Min 1 min |
| Role | Access |
|---|---|
| Readonly | View volumes, reports, rules, and configurations. Cannot make changes. |
| User | Everything in Readonly, plus activate and deactivate autoscaling and create and manage autoscaling rules. |
| Admin | Everything in User, plus edit configurations, manage users and accounts, configure the AWS IAM Role ARN, and generate API tokens. |
| Generated from | Scope | Use for |
|---|---|---|
| A specific sub-account | That sub-account only | Agent installation, API calls scoped to a single account |
| The organization view | The organization and all its sub-accounts | API calls across multiple accounts (with the accounts= parameter), Terraform-driven account management |
Autoscaling Activation Widget
Optimization Actions table in the Reports page
Autoscaling Storage Size and Monthly Savings Widgets
Utilization and Usage graphs of autoscaling volumes
Utilization and Usage graphs of non-autoscaling volumes
| Tag | Description |
|---|---|
Managed-By: Datafy.io | Identifies the snapshot as managed by Datafy |
datafy:source-volume:id | Volume ID of the original volume before autoscaling. The volume ID associated with the snapshot by AWS is the smaller volume after autoscaling. |
datafy:snapshot:id | A snapshot ID generated by Datafy (designated with the prefix dsnap) , shared by all of the related snapshots created when snapshotting an autoscaling volume. |
datafy:snapshot:generation-id | Generation number of the Datafy snapshot. The first snapshot taken during activation is generation 0, and every following snapshot the generation is increased by 1 |
curl -sSfL https://artifacts.datafy.io/attach_tool | sh -s -- vol-04d316aeec130176a /dev/nvme1n1 vol-07b9a47caa69e90e2 /dev/nvme2n1
You can find the device name by running the lsblk command
Generated source volume id: vol-01afc3a269acebaf9
Volume attached successfully. New device path: /dev/dvol01afc3a269acebaf9
sudo ./attach_tool vol-04d316aeec130176a /dev/nvme1n1 vol-07b9a47caa69e90e2 /dev/nvme2n1
Representation of "Cluster name contains dev or prod"
For consistent results, use Gi units when defining volume sizes
Only iops and throughput can be modified this way. Any other parameter in the class is rejected. Setting IOPS or throughput through the PVC annotations used by volume-modifier-for-k8s is not supported for autoscaling volumes.
curl -sSfL https://agent.datafy.io/install?version="$VERSION" | AGENT_MODE="autoscaler" TOKEN="$TOKEN" sh
# The volumes will typically appear as /dev/nvme1n1 and /dev/nvme2n1
# Adjust the device names below if yours are different
# Create ext4 filesystems on both volumes
sudo mkfs.ext4 /dev/nvme1n1
sudo mkfs.ext4 /dev/nvme2n1
# Create mount points
sudo mkdir -p /mnt/vol1 /mnt/vol2
# Mount the volumes
sudo mount /dev/nvme1n1 /mnt/vol1
sudo mount /dev/nvme2n1 /mnt/vol2
# Add to fstab for persistence across reboots
echo "$(blkid -s UUID -o value /dev/nvme1n1) /mnt/vol1 ext4 defaults,nofail 0 2" | sudo tee -a /etc/fstab
echo "$(blkid -s UUID -o value /dev/nvme2n1) /mnt/vol2 ext4 defaults,nofail 0 2" | sudo tee -a /etc/fstab
Datafy Virtualization Layer