@danieldibswe@ozgurgulerx@AWSSupport Nothing specific. This is about knowing your AWS service limits which is only relevant when you get "what is the max I can do for ..." questions we get frequently...
Q-On #TGW you can have X4 connect peers over each TGW connect att. So this is X5 attachments per #SDWAN headend connectivity (why?). You can have 1k of these. You are bound by the max TGW att limit of 5k per TGW. However won't work. Where would the bottleneck be? @AWSSupport
These capabilities (e.g. event debugging) needs to be offered optionally for advanced practitioners. Not every instance is suitable for support tickets.
For anyone from networking (applies to a wider audience ), it is difficult to get used to AWS. The complexity is abstracted to lower the tech barrier for increased adoption as always.The problem is you need to be able to look under the hood when things go wrong which you cannot.
The design choice made for #TransitGateway#IPv6 Connect attachments looks a bit backwards for today. The only way this works is establishing IPv6 address-fam neighborships over IPv4. BGP IPv6 neighborships will not work...Still very useful, but why? https://t.co/n9fp5zCCOm
These two sessions are from a time where networking landscape was much simpler and therefore give an easier entry to Direct Connect details. @AWSSupport
NET402 AWS re:Invent 2016: Deep Dive: AWS DX and VPNs
NET403 - AWS re:Invent 2017: Deep Dive: AWS DX and VPNs