Kinda sucks for images that license to the network interface. They added elastic network interfaces, but you can't use those for eth0 (which a lot of software licenses to), so you're still screwed
tl;dr In the VMware world you've always had the ability to specify your own MAC and IP address. In VMware Cloud on AWS you'll have the same ability.
I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...), so I can't fully comment on your situation, but it seems you could find out what specifically the license is attaching to and set that up again (if it's MAC, you just override the MAC, etc...).
The software I've used that bound to the CPU (which is silly as well) always had a mechanism to "de-register" the software specifically for migrating to new hardware. So you could setup your vm, install all your software, etc... then de-register the software (but leave it installed). Make your "appliance" image (OVA), import to the new "cloud" and re-register your application.
This is super, super common with legacy software products narrowly scoped to very specific business functions.
This was super super super super fun on IRIX when NIC died. Usually in the midst of work chaos.