Site A and Site B have access to two separate NAS storage. For purposes of simplicity, datastore names were kept the same across both arrays.
Below shows datastores in Site A.
Below shows datastores in Site B.
In the case of VMware Cloud on AWS, which uses vSAN storage internally, all VMs running inside the cloud SDDC consume storage capacity and leverage storage services from the vSAN datastore. Management workloads and the workloads belonging to a single VMware Cloud on AWS customer are located on the same vSAN cluster.
However, the cloud SDDC introduces a new vSAN capability that provides two logical datastores instead of one. One of these datastores ‘vsanDatastore’ is used to store the management VMs; the other datastore ‘WorkloadDatastore’ is used for the customer VMs.
VMware creates and operates a separate resource pool to manage customer workloads. Customers have the option of creating child resource pools but cannot configure cluster affinity rules at initial availability.
Keep in mind the current solution is deployed on a 6 Node Stretched Cluster for VMware Cloud on AWS across 2 AZ’s , 3 ESXi servers per AZ , so RAID 5 / 6 option is not available.
More information on vSAN Storage Policies and RAID configuration options on VMware Cloud on AWS can be found here.