Automate setting up and managing your transit networks with AWS Transit Gateway

Guidance for Network Orchestration for AWS Transit Gateway automates the process of setting up and managing transit networks in multi-account AWS environments. It creates a web user interface (UI) to help you control, audit, and approve or reject transit network changes. The Guidance supports both AWS Organizations and standalone AWS accounts, and you can visualize your transit network across multiple AWS Regions. You can use the default deployment template or customize it to meet your specific use case.

You can use AWS Transit Gateway to attach Amazon Virtual Private Clouds (Amazon VPCs) in the same AWS Region, and to route traffic between them. With this deployment, you can connect your VPCs across multiple accounts by tagging the VPCs. It also connects your transit gateway across multiple AWS Regions by tagging the transit gateway. You can set rules to automatically approve or reject, or manually approve, the network changes.

This implementation guide provides an overview of the Guidance for Network Orchestration for AWS Transit Gateway, its reference architecture and components, considerations for planning the deployment, and configuration steps for deploying it to the Amazon Web Services (AWS) Cloud.

The intended audience for this implementation includes solution architects, networking professionals, business decision makers and cloud professionals. To deploy and use it, you should have an understanding of Amazon VPC, route tables, subnets, transit gateways, and network protocols. For additional training about these topics, see AWS Networking Basics, Understanding AWS Networking Gateways, and Advanced Architecting on AWS.

Use this navigation table to quickly find answers to these questions: