AWS Transit Gateway Orchestrator Build¶
At Build stage, you attach VPCs to an AWS Transit Gateway (TGW) and security domain. Each VPC can only be attached to one security domain.
AWS Transit Gateway (TGW) Orchestrator Build workflow is a one step instruction to attach VPC to AWS Transit Gateway and security domain.
For background information, refer to TGW Orchestrator FAQ.
Before you can attach VPCs, you must have at least completed Step 1 in Plan page.
1. Attach VPC to TGW¶
|Region||Select a region where AWS Transit Gateway resides.|
|VPC Account||An Aviatrix account that corresponds to an IAM role or account in AWS.|
|VPC Name||Select a VPC in the VPC Account.|
|TGW Account||Select an access account where AWS Transit Gateway resides.|
|TGW Name||The name of the AWS Transit Gateway in the AWS Transit Gateway Account.|
|Security Domain Name||Select from a drop down menu domain.|
|Advanced (Optional) Select Subnets||Available from R4.3 and later. When selected, a drop down menu of VPC subnets appears for you to multi select subnets/AZs should be attached to the VPC. For a MAC keyboard, use Command key and select. For a Window’s machine keyboard, use Control key and select. When not selected, Aviatrix Controller automatically select a subnet representing each AZ for the VPC attachment.|
|Advanced (Optional) Customize Spoke VPC Routes||Available from R4.7 and later. When you customize the Spoke VPC route entries, no learned routes are programmed into the VPC route table. If you wish no route to be programmed by Aviatrix Orchestrator, enter 0.0.0.0/32.|
For example, you can attach a VPC to prod_domain created at the Plan page, as shown below.
2. Detach VPC from TGW¶
This step detaches a VPC from a AWS Transit Gateway and Domain.