Onboarding experience of VMware ON AWS in Production Environment-Part2
VMware ON AWS Deployment - Requirements.
As mentioned in the previous post , when we are set with the project objective, we need to prepare the items mentioned in the VMC deployment checklist. Some of the basic requirements are,
- The AWS account details - When we deploy our SDDC on VMware Cloud on AWS, it is created within an AWS account and a VPC dedicated to your organisation and managed by VMware. We must also connect the SDDC to an AWS account belonging to us, called the customer AWS account . This connection allows our SDDC to access AWS services belonging to our org account.
- SDDC Management subnets - This is the most critical part of the deployment. Choosing the right network for SDDC and connect back to ON-Premise network (check with network team to make sure you provide unique range of CIDR, ASN etc to avoid conflicts)
- Connectivity to On-Premise DC and VMC - There are different ways to connect to the On-Prem DC, using IPsec VPN, AWS Direct Connect, Hybrid Cloud Extension (HCX) /HCX Connector, or custom MPLS, network backend connections. ( example AT &T Netbond)
- Region where we deploy the VMC SDDC stack ( we need to choose from AWS Regions)
- Cluster type - We have an option to choose either Stretched or non-Stretched Cluster
- Number of hosts do we need in the SDDC cluster ( remember we can start from 1 host but the recommended settings for production cluster is minimum of 3 nodes )
Getting Started with Deployment:
Post deployment Steps:
1. The landing page : In this page, we can check the summary of our deployed SDDC components, region where we deployed the stack, etc.
Below is a more detailed view of how NSX is deployed within VMware Cloud on AWS (diagram courtesy of Gilles Chekroun)
We will see how to connect to ON-Premise datacenter from our VMC setup in our next blog post