Connect to Your Network using AWS Transit Gateway

Intro

AWS Transit Gateway (TGW) is a "hub-and-spoke" router provided by AWS, used to scalably connect AWS Virtual Private Clouds (VPCs) to another. TGWs sit on top of your Virtual Private Network (VPN) and provide a single site-to-site point of contact.

Since each Nautobot account comes with a TGW of its own, your network has multiple ways to connect to it:

1. We-share-ours: We share your Nautobot Cloud account's dedicated TGW with you so that you can connect to it without having one yourself.
2. You-share-yours: You provide a TGW for your VPC, sharing it via Resource Share in AWS RAM (Resource Access Manager).
3. Peering TGWs: TGWs on both sides connect to each other without any AWS resource-sharing.

Network diagram of Nautobot cloud connectivity via AWS Transit Gateway. Different configurations are overlaid.

Comparison Chart

• Pros

  Flexible TGW configuration options between your VPC and Nautobot

  Centralized routing and security inspection

  Hub-and-spoke model supports multiple external connections without complex meshing or routing tables

• Cons

  Requires an AWS Account

  Must route any on-prem networks through an AWS VPC to be accessible by Nautobot

  May be unsuitable for SLA-level performance and compliance

  No self-serve setup (contact support)

How Get started

To connect using AWS Transit Gateway, please submit a ticket through our support portal.

OPEN A TICKET

Further Reading

AWS Transit Gateway (aws.amazon.com)