Route · AWS → Zadara

Migrate VMs from AWS to Zadara

Z-Move, the agentless VM migration platform, copies the EBS disks of your EC2 instances into a Zadara region, registers an image ready to launch and starts a test VM that has to answer on SSH or RDP. Nothing is installed in your instances, and they keep running during the copy.

At a glance

The route, measured

AWS → Zadara

In production
How it runs

Relay. A worker in AWS reads an EBS snapshot and streams it to an import worker in Zadara.

You get

A Zadara image, ready to launch.

Operating system

Linux boots as it is: the VirtIO drivers ship with the kernel. For Windows, check the VirtIO drivers before the cutover.

Measured run
8 GiB1 disk
17mtotal time
1m 21suntil SSH answered

Validation run, AWS US East to Zadara, with boot test. The transfer ran at 12.4 MB/s with no reconnects, and the source set the pace: a volume restored from an EBS snapshot fetches each block from Amazon S3 the first time it is read.

Boot test
Passed: SSH answered on port 22.
Z-Move session page for a completed AWS us-east-2 to Zadara br-ftz-1 migration: 2 disks, 19.0 GiB, 20m 29s in total, 19.3 MB/s on average, image created.
A completed AWS US East (Ohio) → Zadara session: 2 disks, 19 GiB, 20m 29s from start to finish. Names from the demo environment.

How an AWS to Zadara migration runs

  1. Add an AWS access key for the source account and the keys of the Zadara region. Both are encrypted and deleted 30 days after the job ends.
  2. Pick the EC2 instances, or an EBS snapshot or an AMI. Several instances run as a batch, one job each, into the same Zadara region.
  3. Pre-checks confirm the credentials, the disks, the operating system, the image name and recent quota errors before anything starts. A Windows instance gets a warning about VirtIO drivers.
  4. Z-Move creates an image of the instance without rebooting it, which takes a snapshot of every disk, and starts a temporary worker in your AWS account. The worker makes volumes from those snapshots and streams them over TLS, through the Z-Move relay, to an import worker already waiting in Zadara. The data passes through memory and is never written to disk on the way.
  5. The import worker writes the Zadara volumes, snapshots them and registers the image. The workers, the temporary volumes and the snapshots Z-Move created are deleted, and the session lists every resource it created and removed.
  6. From the job page, a boot test starts a VM from the new image in Zadara. It passes when the system answers on SSH, RDP, HTTPS or HTTP.
Migration wizard, source step: AWS US East (Ohio) region and access keys.
Wizard · source · AWS US East (Ohio)

Linux boots as it is

The VirtIO drivers that Zadara uses ship with the Linux kernel, so a Linux instance from AWS boots on Zadara without changes. In our runs cloud-init worked on Zadara without any adaptation, and the boot test passed with SSH answering on port 22.

Windows has also been migrated on this route: the disks are copied block by block and the licence comes with the image. Before the switch, make sure the image has the VirtIO drivers that Zadara uses; the pre-checks warn you about them.

Before you switch

The image carries the disks. What belongs to the AWS account stays there, so check these before you move traffic:

  • Security groups, Elastic IP addresses and load balancers: recreate in the Zadara region what the VM needs.
  • IAM instance profiles: applications that call AWS APIs with the instance's role need credentials of their own on Zadara.
  • IP addresses change: update DNS records, allow-lists and anything else that points at the old addresses.
  • Only the volumes attached to the instance when the job starts are copied.

Downtime and rollback

Z-Move copies a snapshot, so the instance 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 instance before you launch the job: the downtime is then the copy time of that VM.

Rolling back means carrying on with the AWS instance, which stays untouched until you decide to retire it.

What it costs

Z-Move bills US$0.05 per GiB written to Zadara: 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 data that leaves AWS, the temporary worker instance and its public IPv4 address (AWS bills public IPv4 addresses by the hour), and the snapshots and volumes it uses. They are deleted at the end.

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

AWS to Zadara: questions

Something else? Write to hello [at] zmove.click

Do I need to install anything on my EC2 instances?

No. A temporary worker in your AWS account reads a snapshot of each disk. Nothing is installed in the instance, and the instance is never stopped or changed.

Can I move several instances at once?

Yes. Select several instances, snapshots or AMIs in the wizard: Z-Move creates one job per resource and runs them one after another into the same Zadara region.

Can I start from an EBS snapshot or an AMI?

Yes. The source can be a running instance, an EBS snapshot or an AMI. Snapshots and images you pick as the source are never deleted; only the snapshots Z-Move creates itself are removed after a completed migration.

Does the instance have to be stopped?

No. The copy is crash-consistent. For databases and other applications that write a lot, stop the application or the instance first to get a consistent copy.

What does the AWS access key need?

EC2 permissions only, no IAM role: read instances, volumes, snapshots and images; create an image of the source instance and volumes from its snapshots; launch, tag and terminate a temporary worker; create its security group and a temporary public IP; and delete the volumes, snapshots and image it created. A least-privilege IAM policy, limited to the resources Z-Move tags and names, is available on request.

Can I migrate encrypted EBS volumes?

Z-Move does not change encryption: the volumes it creates from your snapshots keep the snapshot's encryption. With a customer-managed KMS key, the key must allow the access key to use it through EBS. Encrypted sources have not been part of our measured runs yet, so tell us before you migrate one.

How long does it take?

It depends on the data and on how fast EBS serves it. In a measured run, an 8 GiB instance took 17 minutes from start to finish, and SSH answered on Zadara 1m 21s after the boot test started.

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

We only use these details to reply to you.