This epic is about creating a rpovider to imoprot Vms from EC2.

It's the successor of the workaround: MTV-2814

Things to consider:

Inventory from an EC2 region

Verification of a provider ( credentials, permissions ... )
Verification of VMs, .rego files for the new provider
Verification of Plan, what the new provider capability ( only cold migration, only to target = "ROSA", only on same region, storage mapping can only map on the same storage )

Storage moving, snapshot book keeping, creating PV using same storage ( and PVC and DV for kubevirt benifit )
Storage moving, keep it modular for moving on different storages ( using dd, cdi, ... ? )

Image conversion, will virt-v2v work on none vmware images ?

VM building, special preferences ?

Not in scope:

 - Target not  ROSA
 - Target not owned by same account
 - Target on different region
 - Warm or Live migrations