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.
There are many tools that can be used to interact with the VMware Cloud on AWS API: through the API Explorer, Postman, curl, The Python Client for VMware Cloud on AWS, or other tools. In this post, I have documented common organization, account linking, and SDDC operations customers might leverage in order to build and maintain an SDDC.