RAID-1 is a mirror configuration that provides high availability by creating multiple copies of a VMDK. RAID-5 and RAID-6 are erasure coding configurations that provide fault tolerance by distributing data and parity across multiple hosts.

The number of failures to tolerate (FTT) determines how many copies or parity blocks are created for each VMDK. For example, RAID-1 FTT = 2 means that there are three copies of each VMDK.

Therefore, based on your requirements, a possible VM storage policy setting could be  RAID-1 FTT = 2 , which would provide redundancy at the highest level possible with six hosts.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-EDBB551B-51B0-421B-9C44-6ECB66ED660B.html

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-ED8B84E8-BF1C-47EE-BB60-8D5741351822.html

By default, the management gateway firewall is set to deny all traffic between the internet and vCenter Server. Verify that the appropriate firewall rules are in place.

The administrator can create an NSX firewall rule in the VMware Cloud data center that allows access to the vCenter from the on-premises data center. This would allow the VPN connection to connect to the vCenter, allowing the administrator to access and manage the VMware Cloud environment.

Incident and Problem Management: VMware will provide incident and problem management services (e.g., detection, severity classification, recording, escalation, and return to service) pertaining to availability of the Service Offering. VMware is responsible for incident and problem management (e.g., detection, severity classification, recording, escalation, and return to service) pertaining to all virtual machines that you have deployed in your SDDC.

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/vmw-cloud-aws-service-description.pdf

https://cloud.google.com/vmware-engine/docs/concepts-vmware-components Node Considerations

You can specify the number of hosts to add or remove to or from their cluster.

Private cloud initial setup happens in ~30 minutes.

Additional hosts can be added in ~15 minutes.

A three-node cluster is the minimum for production.

You can have up to 32 hosts per cluster.

You can have up to 64 hosts per private cloud.

https://cloud.google.com/architecture/private-cloud-networking-for-vmware-engine

Dedicated Interconnect provides a private [1] [2] , dedicated connection between your on-premises network and Google’s network. It offers low latency, high bandwidth, and a secure connection. Partner Interconnect provides a connection to Google Cloud Platform through a partner’s network, such as a service provider or a carrier. It offers the same low latency, high bandwidth, and secure connection, but is slightly slower than Dedicated Interconnect.

References: [1] https://cloud.google.com/interconnect/docs/concepts/types [2] https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.networking.doc/GUID-6D3A8E3B-A7B1-4A05-A9A8-C4F4A4A4C1A2.html

VMware High Availability (HA) is a feature of the VMware Cloud platform that monitors the health of virtual machines and restarts virtual machines on other hosts if they crash or become unresponsive. This ensures that the virtual machines are always available and that no downtime is experienced. The default response is to restart the impacted virtual machine on other hosts in the same SDDC Cluster, however, this can be customized to suit the needs of the customer.

References: [1] https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.availability_and_scalability.doc/GUID-C7E2C2A2-B9A8-4CD0-A2F2-EA6C08C8D95B.html [2] https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.admin.doc/GUID-F9C7F1B8-4855-4C3A-A723-C9A2F7CDBFFB.html

https://blogs.vmware.com/cloud/2019/07/02/dhcp-dhcp-relay-vmware-cloud-aws/

To create a new network segment in the software-defined data center that utilizes the corporate DHCP server to provide IP addresses, the proper sequence is to create a DHCP relay profile, create a new segment attached to the Tier-1 gateway, and configure the segment DHCP config to utilize the new DHCP relay profile 1 .  This is because the DHCP relay profile contains the IP address of the external DHCP server and the DHCP relay agent that forwards the DHCP requests and responses between the segment and the DHCP server 1 .  The segment must be attached to the Tier-1 gateway, which is the edge device that provides routing and firewall services for the segment 2 .  The segment DHCP config allows the administrator to specify the DHCP type, the DHCP relay profile, and the DHCP options for the segment 3 .  References :  1 : Configure Segment DHCP Properties - VMware Docs,  2 : Create or Modify a Network Segment - VMware Docs,  3 : Segment DHCP Config - VMware Docs

According to  1 , VMware NSX-T Data Center implements three separate but integrated planes: management, control, and data.

The management plane provides a single point of configuration and REST API entry-points for NSX-T Data Center components.

The control plane is responsible for computing network state based on configuration from the management plane and topology information from transport nodes.

The data plane consists of transport nodes that provide connectivity for workloads and enforce network policies.

Overview of NSX-T Data Center: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/installation/GUID-10B1A61D-4DF2-481E-A93E-C694726393F9.html

https://docs.aws.amazon.com/whitepapers/latest/sddc-deployment-and-best-practices/deploying-vmware-cloud-on-aws-sddc.html This 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.

A valid management network CIDR based on the requirements is 10.1.0.0/20, as this provides a range of 4096 IP addresses, which is more than enough for 30 hosts. A /23 CIDR only provides 512 IP addresses, which is not enough for 30 hosts, while a /24 CIDR provides 256 IP addresses and a /16 CIDR provides 65,536 IP addresses, which is more than is needed for the 30 hosts.

https://blogs.vmware.com/cloud/2019/10/03/selecting-ip-subnets-sddc/