What problem does it solve?
Connecting many VPCs and on-premises networks with point-to-point peering creates an unmanageable mesh, and misconfiguring a central transit gateway can silently drop traffic or expose isolated environments. This Skill provides guided, security-hardened procedures for building and operating AWS Transit Gateway correctly.
Core Features & Use Cases
- Hub and Attachment Setup: Create a Regional transit gateway, attach VPCs with one dedicated subnet per Availability Zone, and check for overlapping CIDRs before attaching.
- Segmentation and Inspection: Isolate environments with route tables, centralize egress through a GWLB or appliances, and force east-west traffic through AWS Network Firewall with appliance mode.
- Hybrid and Multi-Region Connectivity: Connect on-premises networks over Site-to-Site VPN (with ECMP and accelerated VPN) or Direct Connect, peer transit gateways across Regions, and migrate off a VPC peering mesh without dropping traffic.
- Use Case: A platform team needs to connect 20 VPCs across two Regions, isolate production from development, and route all outbound traffic through a central inspection VPC. The Skill walks them through hub creation, route table segmentation, and GWLB-based egress with the correct forward and return routes.
Quick Start
Ask the agent to create a transit gateway in us-east-1 and attach your VPCs with segmentation disabled by default, then follow the matching reference for your specific routing goal.