AWS re:Invent 2018: [NEW LAUNCH!] Introducing AWS Transit Gateway (NET331)

To deliver your applications to millions of users you need to scale your network across thousands of VPCs. AWS Transit Gateway helps scale your workloads and vastly simplifies how you connect your AWS networks. AWS Transit Gateway also makes it easier to connect your on-premises networks across those VPCs. Using secure operational controls, you can implement and maintain centralized policies to connect Amazon VPCs with each other and with your on-premises networks. This session will enable you to get started quickly and get an insight into the various capabilities that AWS Transit Gateway introduces.

[@worldexplorer796]

I have watched both Transit gateway videos (331 and 402). Liked both. However this session is deep dive and especially the 'Association' and 'propagation' has been explained which so far not in documentation. Well done

[@PrasadChitibomma]

Transit Gateway is fully managed service, helps to manage connectivity among multiple VPCs, on-prem with one time changes at customer gateway. awesome presentation 👍

[@prashh83]

Great concept , it will simplify the network connectivity.

[@victornjoroge562]

Great presentation..Thanks

[@smihsmih88]

Hi Senthil- just wanted to let you know that Aviatrix Orchestrator for Transit Gateway further simplifies routing for segmented routing topologies without manual updates to TGW Route Tables. (Disclaimer I work for Aviatrix and we presented in the NET209-L session, 42:00 mark) thanks!

[@cheethoe]

​ +Steve Seymour If you're creating new subnets purely for VPC attachment, is there a recommended size for this subnet?

[@devagrawal03]

Let's say if I have 10 VPN connection in on-prem and I connect that with Transit Gateway, Can the 10 VPN would be talk to each other and the VPC connected to TGW ?

[@staj]

This was fantastically done! I only have to figure out now the difference between VPC peering options and Transit Gateway other than the connection to the CGw i.e. vpc peering is already taken care of using Transit Gateway, so what 's the need for the vpc peering options? #researchmodeactivated

[@vishalkhatri3600]

Slide with Title " The Default" at around 15 minutes showing TGW Route table entry 10.99.99.0/16. Shouldn't it be 10.99.99.0/24 which is CIDR for On-Prem unless I am missing something?

[@vishalkhatri3600]

Can anybody please respond on this or let me know if I am looking at wrong place. I hope its just typo in here slide. Enlightening presentation though

[@cabc74]

Is it me or the service is very expensive? I mean, when you start adding a few connections the fixed price goes up and you also pay traffic. Sure it may be simpler an less expensive than the previous transit VPC solution with EC2 instances, but that was a hack to solve a lack of a simple native service. Looks like NAT gateway, that is a glorified internet gateway at high price.

[@43garg]

is it possibble to get this PPTs ?

[@steveseymour9928]

Sumit Garg The slides are now available at www.slideshare.net/AmazonWebServices/new-launch-introducing-aws-transit-gateway-net331-aws-reinvent-2018

[@diepanhrabbit6100]

great service. can you guy point me the slice for this talk? thanks!

[@steveseymour9928]

DiepAnh Rabbit - slides have now been uploaded to www.slideshare.net/AmazonWebServices/new-launch-introducing-aws-transit-gateway-net331-aws-reinvent-2018

[@homedworak]

do trees have ROOTs or ROUTES?

[@MarcoBazzani-MB]

Alleluia

[@ibmuser13]

Marco B. Hare Krishna

[@pier5498]

If only the presenter wearing the T-shirt spoke a bit slower so we can actually grasp, absorb and process what he's saying. Great presentation otherwise.