VMware on AWS - Import-VApp not working when used outside of the SDDC

[Space-Venom]

Hi, I am automating a process of SDDC deployment in VMC. One of the goals is to deploy the whole system automatically, including the networks, firewall rules, and VMs. I have discovered that when I attempt to use ovftool or PowerCLI Import-VApp cmdlet, they fail due to timeout. Netstat clearly shows they attempt to communicate with the ESXi directly. The same problem does not occur when using the vCenter "deploy OVF" wizard; it means that the deployment process used in the GUI is not the same. I am aware this could be resolved by establishing a VPN or running the command from a linked VPC, however, this would make the deployment process more complex. Perhaps fixing the Import-VApp to support SDDC deployment would not be so difficult?..