In this session, I presented the common customer connectivity designs, and discuss considerations, constraints, and features that need to be considered when designing connectivity between VMware Cloud on AWS with existing data centers, AWS native resources, and, the public internet.
I had a great time presenting at AWS Summit at McCormick Place at the Apollo Theater. I wanted to post some pictures of the event. The session was titled “Modernize your applications and move to the cloud while satisfying IT Ops and Finance.” It was a great experience!
We can now build a production SDDC from the API. This will be a multi-step process, including finding the account-linking url, running the AWS CloudFormation Template, finding the the compatible VPC and subnets, and deploying the Software Defined Data Center (SDDC). I have documented the required API calls to find the required information in several pages, and will refer to them as needed.
In a previous post, I showed how to setup the in Postman environment and configured authentication, let us check out how the access token is stored in the variable for future use in accessing the VMware Cloud APIs. We will validate the Access token returned is stored as a variable for future use.
VMware Cloud users can choose to leverage REST based APIs in order to provision and manage all aspects of VMware Cloud on AWS, Software Defined Data Center (SDDC), NSX configuration, and more. I wanted to write my steps to get started and dive into the authentication structure to generate an access token as a building block for future posts.
One of the unique features of VMware Cloud on AWS (VMC) is stretched clusters. It allows customers to run their VMs and provide resiliency across AWS availability zones (AZ) without having to re-architect an application. At a basic level, it works by creating a vSAN stretched cluster across two AZs, with a third AZ hosting …
Workload Resiliency and Management with Stretched Clusters in VMware Cloud on AWS Read More »