The .vmdk file contains the virtual machine's hard disk configuration and is preventing the administrator from increasing the disk size. The .vmdk file must be edited to allow the administrator to increase the disk size. More specifically, the administrator must edit the descriptor file within the .vmdk file to change the capacity of the disk.

https://docs.aws.amazon.com/whitepapers/latest/sddc-deployment-and-best-practices/deploying-vmware-cloud-on-aws-sddc.htmlThis must be a RFC1918 private address space (10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16) with CIDR block sizes of /16, /20, or /23. The management CIDR block cannot be changed after the SDDC is deployed. Choose a range of IP addresses that does not overlap with the AWS subnet you are connecting to. If you plan to connect the SDDC to an on-premises DC or another environment, the IP subnet must be unique within your enterprise network infrastructure. Choose a CIDR that will give you future scalability.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-91C57891-4D61-4F4C-B580-74F3000B831D.html

Hybrid Linked Mode can tolerate a time skew of up to ten minutes between the on-premises data center and the cloud SDDC. The maximum latency between your cloud SDDC and on-premises data center cannot exceed 100 msec roundtrip.
https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-BE75F0F1-2864-4926-97FE-37E635471C43.html

VMware Multi-Cloud Vision enables customers to deliver a consistent management and operations layer across any cloud, and to modernize applications in the cloud of choice using the cloud-native services of that cloud provider. It does not run workloads in the cloud to eliminate security issues, standardize at the DevSecOps and infrastructure level, or reduce the number of developers to increase productivity.