AWS Transit Gateway Orchestrator Design Patterns¶
Many design patterns exist to deploy your network with the AWS Transit Gateway Orchestrator. Here are some examples.
While the design pattern diagrams use a single symbol to represent the Aviatrix gateways, all designs can be implemented with multi-AZ high availability.
Dev & Prod isolated design¶
If you like to build network segmentation between Dev/QA VPCs and Production VPCs, but require shared service VPC and on-prem to reach each VPC, consider the diagram below. diagram below.
In this network design, you need to create two custom Security Domains, Dev_Domain and Prod_Domain.
At the Plan page Step 2, select “Create Custom Security Domain” and fill in the information. Make sure you multi select Shared_Service_Domain and Aviatrix_Edge_Domain for “Connect to Security Domains”. Apply this step for both Dev_Domain and Prod_Domain.
Dev & Prod isolated design with TGW Direct Connect or VPN¶
Aviatrix integrates native TGW Direct Connect and VPN to connect to on-prem while allowing you to connect to multiple cloud as Spoke VPCs.
All-in-cloud with Multi Security Domains¶
If you are only concerned about VPC to VPC segmentation, you can deploy Aviatrix Controller for an all-in-cloud segmented network, as shown below.
Connecting Transit Gateways in Multi Regions Multi Cloud¶
You can use Aviatrix Transit GWs to connect AWS Transit Gateways in multi regions and multi cloud deployment, as shown below.
TGW Orchestrator for cross region and multi cloud spoke¶
You can extend the TGW to a different region with transit peering and then spokes in a different cloud.
Full mesh network design¶
If you like to build a full mesh network that allows all VPCs and on-prem to communicate with each other, you do not need to create any custom Security Domains. Simply use the built-in Default_Domain and Aviatrix_Edge_Domain for the deployment, as shown below.
At Plan page Step 2, select “Full mesh network”.
Fully Isolated network design¶
If you would like to build a fully isolated network where no VPC can communicate with each other except to the shared service VPC and on-prem, you need to create a Security Domain for each VPC and connect each domain to the Shared_Service_Domain.
In this network design, you need to create a custom Security Domain for each VPC.
If this design does not scale for you, consider the Aviatrix Transit Network workflow where all VPCs are by default isolated to each other.
Fully Isolated network with multi sites VPN¶
You can use TGW native VPN capability to connect to multi sites VPN. Since VPN connection is in Default Security Domain, you need to build connection policy for each VPC domain.
Integrating with Distributed Egress Control Design¶
For any of the TGW design patterns, you may deploy Aviatrix distributed Egress FQDN in each VPC. In this example, a full mesh deployment is expanded to include Egress FQDN support, as shown below.
Follow the instructions for FQDN to deploy egress control function.
High Performance Transit - Insane Mode¶
Deploy an Aviatrix hardware appliance on-prem to achieve 10Gbps Transit Network throughput. Added benefit is that traffic over Direct Connect is encrypted.
Simplify and scale your firewall deployment with Aviatrix Firewall Network solution. For more information, check out Firewall Network FAQ.
TGW Native Hybrid Network¶
Aviatrix supports TGW VPN and TGW Direct Connect for connecting to remote site or on-prem network, as shown in the diagram below.
Secure Transit with DMZ Firewalls¶
Firewalls can be deployed in the Transit VPC for a centralized Ingress and Egress security solution, as shown below. .