Route · Zadara → AWS
Migrate VMs from Zadara to AWS
Z-Move, the agentless VM migration platform, copies the disks of your Zadara VMs into an AWS region and registers an AMI that current EC2 instance types accept. A boot test then starts an instance from it before you switch. Nothing is installed in your VMs, and they keep running during the copy.
At a glance
The route, measured
Zadara → AWS
In productionRelay. A worker in Zadara streams the disks to an import worker in AWS.
An AMI registered with ENA, ready for current instance types.
Linux and Windows are copied block by block, as they are.
Validation run, Zadara to AWS US East. The transfer ran at 71.4 MB/s with no reconnects, and the network set the pace. AWS then took about 2.5 minutes to finish the snapshot behind the AMI. The route is in production at a telecom operator.
How a Zadara to AWS migration runs
- Add the keys of the Zadara region, or paste a custom zCompute endpoint, and an AWS access key for the target account. Both are encrypted and deleted 30 days after the job ends.
- Pick the VMs, or a snapshot or an image. Several VMs run as a batch, one job each, into the same AWS region.
- Pre-checks confirm the credentials, the disks, the operating system, the image name and recent quota errors before anything starts.
- Z-Move creates an image of the VM without rebooting it, which takes a snapshot of every disk, and starts a temporary worker in your Zadara project. The worker streams the disks over TLS, through the Z-Move relay, to an import worker already waiting in your AWS account. The data passes through memory and is never written to disk on the way.
- The import worker writes EBS volumes, snapshots them and registers an AMI with ENA support. The workers and the temporary volumes are deleted, the snapshots Z-Move created in Zadara are removed after a completed migration, and the session lists every resource it created and removed.
- From the job page, a boot test starts an instance from the AMI. It passes when the console shows the system booted, or when it answers on SSH, RDP, HTTPS or HTTP.

An AMI for current instance types
Z-Move registers the AMI with ENA support, which Nitro instance types such as t3, m5 and c5 require. A guest without the ENA driver, such as a very old Linux kernel, still launches on those types but without network, so check it before the switch.
Linux and Windows are copied block by block, as they are. In our runs, cloud-init on the migrated Linux image applied the AWS key pair at launch, and SSH worked with it.
Before you switch
The AMI carries the disks. What belongs to the Zadara region stays there, so check these before you move traffic:
- Security groups and floating IPs: create in your AWS VPC the security groups the VM needs, and an Elastic IP if it needs a fixed public address.
- Key pair: choose one when you launch the instance. Images with cloud-init pick it up; others keep the logins they already had.
- Instance type: any current type works with the ENA-enabled AMI, as long as the guest has the ENA driver.
- IP addresses change: update DNS records, allow-lists and anything else that points at the old addresses.
- Only the volumes attached to the VM when the job starts are copied.
Downtime and rollback
Z-Move copies a snapshot, so the VM keeps running and is never stopped or changed. The copy is crash-consistent, like a server after a power cut. For a database or a busy application, stop the application or the VM before you launch the job: the downtime is then the copy time of that VM.
Rolling back means carrying on with the Zadara VM, which stays untouched until you decide to retire it.
What it costs
Z-Move bills US$0.05 per GiB written to AWS: the data, not the size of the disk. A retry does not pay again for disks already copied.
On your AWS bill, during the job: the temporary worker instance and its public IPv4 address, and the EBS volumes and snapshots it uses; the boot test adds a test instance and another temporary public IPv4 address. AWS bills public IPv4 addresses by the hour. After the job, the AMI's snapshots stay in your account, because they are the image.
Security
The workers carry no secrets of the platform. Each starts with only a token valid for its own job, receives the access key for its side over TLS while the job runs, keeps it in memory, and accepts no connections from the internet. Keys are encrypted at rest and never written to logs. Because the key reaches the worker, the permissions you give it are the real limit: give it only what the migration needs (see the questions below).
See the security overview, the DPA and the subprocessors.
FAQ
Zadara to AWS: questions
Something else? Write to hello [at] zmove.click
Do I need to install anything on my Zadara VMs?
No. Z-Move works with an image of the VM and the snapshots behind it, through the cloud APIs. Nothing is installed in the VM, and the VM is never stopped or changed.
Which instance types can I launch the AMI on?
The AMI is registered with ENA support, so current Nitro types such as t3, m5 and c5 accept it. The guest needs the ENA driver to have network on those types; a very old kernel without it launches without network.
Will the instance use my AWS key pair?
In our runs, cloud-init on the migrated Linux image applied the key pair chosen at launch, and SSH worked with it. An image without cloud-init keeps the logins it had in Zadara.
Can I check that it boots before I switch?
Yes. The boot test starts an instance from the AMI in the target region, opens SSH, RDP, HTTPS and HTTP only to the Z-Move server, reads the console and tries those ports. The test instance and its temporary public IP are removed at the end.
What does the AWS access key need?
EC2 permissions only, no IAM role: launch, tag and terminate the temporary worker and the boot-test instance; create volumes and snapshots and register the AMI; create a security group and a temporary public IP; and read instances, volumes, snapshots and images. A least-privilege IAM policy, limited to the resources Z-Move tags and names, is available on request.
Will the volumes be encrypted on AWS?
The volumes and snapshots Z-Move creates on AWS follow your account's default EBS encryption setting. Z-Move does not set a key of its own. Encrypted targets have not been part of our measured runs yet, so tell us if you use a customer-managed KMS key.
How long does it take?
It depends on the data and the network. In a measured run, a 20 GiB VM took 14 minutes from start to finish: the transfer ran at 71.4 MB/s, and AWS took about 2.5 minutes to finish the snapshot behind the AMI.
Demo
See a full run, from wizard to boot test.
Book a demo and follow a complete migration: wizard, pre-checks, live session, boot test and cleanup.
Or write to hello [at] zmove.click