Updated 29 October 2026 · Published by Zoorik
Short answer. Amoeba lists only running VMs with at least one data disk, from the subscriptions Zoorik can read. A VM that can’t be onboarded is counted in one line under the list, with the reason. Once you onboard a VM, its used space and savings appear after its agent reports.
Read the line under the list
Look at: “Onboard VMs”, and the line under the list.
What it means: VMs that can’t be onboarded are counted in one line under the list, with the reason. For example, the VM is stopped, or it has only an OS disk.
What to do: Fix the reason shown, then open “Onboard VMs” again. The checks below explain what each requirement means.
Check the cloud connection
Look at: the connection’s state in the console.
What it means:
| State | What it means |
|---|---|
Verifying | Zoorik can’t read a subscription yet. The console says why: Zoorik’s app isn’t in your directory yet, the role isn’t assigned, or the directory wasn’t found. |
Connected | Zoorik reads your subscriptions through the role. |
Access lost | Zoorik lost read access to a subscription. Figures from Azure keep their last value, with its date, and onboarding waits. |
What to do:
- For “Verifying”: run the connect script the console shows in Azure Cloud Shell, with your own Azure sign-in. Then click “Verify”.
- The script adds Zoorik’s app to your directory, creates the role “Zoorik Storage Operator”, and assigns it on each subscription you name. You need permission to do all three.
- If the directory wasn’t found, check the directory (tenant) ID you entered in “Connect Azure”.
- For “Access lost”: check the role is still assigned to Zoorik’s app on that subscription. If it isn’t, run the connect script again. Zoorik checks access again regularly.
Check the VM’s subscription is included
Look at: the subscriptions you named when you ran the connect script.
What it means: The script assigns the role only on the subscriptions you name. Zoorik acts in your Azure only through that role.
What to do: Run the script for the VM’s subscription too. Then click “Verify” again: it picks up the subscriptions you added since.
Check the VM is running and has a data disk
Look at: the VM in Azure: whether it is running, and its disks.
What it means: Amoeba lists only running VMs with at least one data disk. It works on data disks and never touches the OS disk. The data on those disks must sit on mounted filesystems.
What to do: Start a stopped VM, then open “Onboard VMs” again. A VM with only an OS disk has nothing for Amoeba to move.
Give the list a moment
Look at: a VM you just created, started or changed.
What it means: The list comes from Azure Resource Graph, which can take a little while to catch up with changes.
What to do: Open “Onboard VMs” again a little later.
On AWS, check the instance
Look at: the EC2 instance, and how the account is connected.
What it means: Amoeba works on EC2 instances that are running and managed by AWS Systems Manager, with the SSM agent connected. Each must be a Nitro type that exposes EBS as NVMe, with at least one EBS data volume. The account connects with its AWS account ID and the IAM role ZoorikStorageOperator.
What to do: Connect the instance to Systems Manager, and check its type and volumes. If the account isn’t connected yet, run the script in AWS CloudShell that creates the role.
Check the agent has reported
Look at: the VM’s agent on Overview, and its figures.
What it means: Amoeba installs its agent on each VM you onboard, through Azure Run Command or AWS Systems Manager. The VM’s agent reads “Installing”, then “Connected” once its first report arrives. Until then, used space and savings read “Available once the agent reports”.
What to do: Wait for the first report. Each VM must be able to reach Zoorik, for the agent’s reports and commands, and the sites the agent downloads from.
If the install failed or the agent stopped
Look at: “Needs you” on Overview, and the VM’s Settings page.
What it means:
- The console says why an install failed: the script failed, Azure refused the run, or the install stalled.
- It also says when Zoorik can’t reach the subscription, or when the first report didn’t arrive in time.
- Amoeba tries again for as long as the VM stays onboarded.
- An agent that stops reporting reads “Disconnected”. Amoeba reinstalls it, but never during a move step or a pool operation.
- Until the agent reconnects, the pool stays mounted but can’t expand or shrink.
What to do: Click “Reinstall” in Settings → Agent. It starts a new install straight away, or when the current step of the move ends. It’s available while the VM is running.
Still stuck?
The Amoeba product guide and the Amoeba FAQ have the full detail.
Email founders@zoorik.com, or pick a time to talk (opens in a new tab). Tell us what “Onboard VMs” and the VM’s agent show. Remove tokens, keys and other secrets from anything you send.