vmc-on-aws-trial
VMC-on-AWS-Trial
Goals
- Successfully sign up for VMC on AWS Trial
- Create (VMC) SDDC
Pre-requisites
- VMware Customer Connect Account
- AWS Account
Trial Period (30 Days)
Sign up for the free trial, my assumption is that you will need a justifiable use-case. For me I have a registered company name with a matching domain name. When VMware reached out I gave them my justification and it was accepted! 30 Days of VMC on AWS!
You can signup for the trial period here: VMC on AWS Trial Signup
Vendor Documentation regarding the trial: VMC on AWS Trial Official Documentation
Reference Architecture: Getting Started with VMC on AWS Reference Architecture
Super helpful YouTube “Quick Start Series” VMWare Cloud on AWS Quick Start
If you have never used VMC on AWS and would like a primer, I highly suggest trying out the VMware Cloud on AWS - Fundamentals - Hands-on Lab
Networking
On-prem Networks
Name | Subnet | VLAN ID | Usable Addresses |
---|---|---|---|
Management | 10.120.0.0/16 | 10 | 10.120.0.1 - 10.120.255.254 |
user-vlan-11 | 192.168.250.0/24 | 11 | 192.168.250.1 - 192.168.250.254 |
VMC on AWS (example)
Component | Value | Usable Addresses |
---|---|---|
AWS Region | us-east-1 | n/a |
VPC Name | VMC-VPC | n/a |
VPC CIDR Block | 10.100.0.0/21 | 10.100.0.1 - 10.100.7.254 |
SDDC Name | SDDC-1-DAF1 | n/a |
SDDC Management CIDR Block (default) | 10.2.0.0/16 | 10.2.0.1 - 10.2.255.254 |
Create VPC Subnets as needed (example)
Subnet Purpose | Availability Zone A | Availability Zone B |
---|---|---|
Private Subnet | 10.100.0.0/23 | 10.100.2.0/23 |
Connected SDDC | 10.100.4.0/24 | 10.100.5.0/24 |
Public Subnet | 10.100.6.0/24 | 10.100.7.0/24 |
Create VPC
Login to your AWS account navigate to your VPC section; from here you’ll want to click on “Create VPC”
Once completed you will have a VPC created that can be used with VMC on AWS; i.e. “VMC-VPC” 10.100.0.0/21
Create Subnets inside of the newly created VPC (VPC-VMC)
For my example since the trial only allows for a single AZ, the subnets I create are for the Private Subnet and Public Subnet show in the VPC Subnets Table
Once completed you will have created something similar to the below in your desired region.
Create SDDC
Now that you have your networking completed on AWS you will have everything you need to get started with your SDDC Build.
You can pre yourself further by going through the “View Journey Map” this will go through the quick start series YouTube videos and has clear instructions on how to get your SDDC installed and operational. Essentially it will guide you through creating a VPC and sort out the logistics (payment, etc).
When you’re ready to build your SDDC you can click “Get Started”
From here you will need a enter some information:
- SDDC Name: SDDC-1-DAF1
- I opted to go with something basic, my on-prem uses all lower case and so I thought this would be good opportunity to switch it up and go with CAPS to differentiate between the two.
- AWS Region: **US East (N. Virginia)
- I’m in the east region so it’s the logical choice for me.
- Deployment: Single Host
- Trial allows for a single host only
- Host Type: I3 (Local SSD)
- Trial allows for I3, I believe I could have selected I4 but went with the lowest option -Number of Hosts: 1
- Single Host option is all that is allowed for the Trial
The rest are pretty much defaults and no advanced configuration - click Next
Assuming you’re already signed into your AWS Console you click on Open AWS Console with Cloudformation Template if not you should have the opportunity to add credentials.
This is just a acknowledge before creating the stack, if you’re good to go, check the box and click Create Stack
From here you will see an overview and stack should be created.
You should now be able to select the VPC and subnet you created earlier.
Management CIDR block, I left blank as it will take the default 10.2.0.0/16
If everything is entered to your liking, you can now Deploy SDDC
The page will change to show you status of your SDDC Build
It’s takes a couple of hours, this might have been close or over the 2hr mark
Once completed you will now be able to explore and start using your SDDC!
Things To Do Next
- Add your on-prem public IP address to the NSX Firewall Rules for remote access to the vCenter Allow Access to SDDC vCenter over Public Internet
- VPN Connectivity from your On-Prem Datacenter to your SDDC. Overview of Network Connectivity Options