AWS Transit Gateway and Multiple Accounts

Gilles Chekroun
Lead VMware Cloud on AWS Specialist

Many Customers start to use AWS transit Gateway and want to be able to attach VPCs un multiple accounts.
Often AWS organisations are split by departments and have separate accounts.
This blog post will go through the detailed setup for the TGW and how to connect VPCs in separate accounts.
For a complete description of VMware Cloud on AWS and TGW, please refer to here.
AWS Shared Resource ManagerLogin to the main account where the TGW was created and create a resource share
Name your share and select the TGW  Add the other account and create the share Verify the share creation Log into the account we just added and look for an invitation Accept the invitation For the purpose of the tests we can use an existing VPC or create a new one. I am using VPC4 with CIDR in the added account. Create a TGW attachment for this new VPC At this stage, we will get a "pending acceptance" status. Go back to the main account and accept Check a…

AWS Transit Gateway and VMware Cloud on AWS

Gilles Chekroun
Lead VMware Cloud on AWS Specialist

With the release of AWS transit Gateway, connecting VPCs to VMware Cloud on AWS became much more easy.
This blog post will go through the detailed setup for the TGW and Firewall rules on VMC.
NSX-T SDDC and the Transit GatewaySince November 2018, all new SDDCs deployed will be NSX-T based.
I am assuming that the reader is familiar with that deployment and will have an SDDC ready.
The goal of the AWS Transit Gateway is to allow easy, scalable and performant connectivity between multiple VPCs.
Our lab setup will be something like the schema below.
Lab SetupOn VMware Cloud on AWS side we have two Logical segments ( and .2.0/24). On segment 1, a small Linux machine (.9) and ubuntu machine (.17). On segment 2 just a small Linux machine (.2) so we can do ping tests.
On the side AWS side, I deployed two VPCs (VPC2 and VPC3) with CIDR of and
In each one I have a small EC2 instance (.159 on VPC2 and .174 …

Create a vCenter Content Library using AWS S3 - Part 2

Gilles Chekroun
Lead NSX Systems Engineer - VMware Europe
23-Sept-2018  UPDATE BELOW !!
A few months ago, I wrote a first part about creating a VMware Cloud on AWS vCenter Content Library using AWS S3. It was not an ideal solution since the indexing was done on the local machine.
Working together with Eric Yanping Cao and William Lam, we laid the foundation for having the complete Content Library in AWS S3 and indexing it directly in S3 without having to transfer any images locally.
Congratulations to Eric who did a fantastic job in python3 using boto3 to access the root S3 bucket and indexing it.

File StructureAlthough AWS S3 is an object oriented service, we can have a pseudo file structure with a root bucket and subsequent folders below it with the various VM templates or ISO files.
NOTE: Make sure you don't have any spaces in the folders name !
For my tests I am using the following structure:

└── ContentLib
    ├── DSL4-4-10
    │   ├── DSL-4.4.10-disk1.vmdk
    │   ├── …