Skip to main content

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, 

  1. 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.
  2. 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) 
  3. 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) 
  4. Region where we deploy the VMC SDDC stack ( we need to choose from AWS Regions) 
  5. Cluster type - We have an option to choose either Stretched or non-Stretched Cluster 
  6. 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: 

Once we have the AWS account details ready, we need to provide that to the VMware backend team to provide us with the subscription. These subscriptions are mapped to our AWS account and ENI's to be attached at the later stage of this deployment 

Once we have a "Welcome" email from VMware, we are ready to go with the deployment. Login to VMC console and click on "Create SDDC" and provide the details as captured in the deployment checklist. 

The SDDC Stack deployment is fully automated and the creation of Datacenter, Cluster, addition of nodes, creation and configuration of vSAN datastore, deployment of NSX Components, etc are fully automatic. 

The wait of approx 2 hours would results us with the fully working setup. 

Post deployment Steps: 

Once the deployment is successful login to vmc.vmware.com console to perform the next 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. 


2. Click on View details to review the connectivity details and configuration page. Note: The connection to on-premise is not yet done - we need to perform additional steps which we cover in the following sections of the blog post. 


3. VMC Network diagram : 

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 

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...