Transit Gateway - number of prefixes from TGW->CGW
With reference to the Direct Connect limit "Number of prefixes per AWS Transit Gateway from AWS to on-premise on a transit virtual interface" (20). My interpretation of this is that if you had, say, 25 VPC attachments on a TGW, 5 CIDRs would not be advertised to the Customer Gateway.
Are the 5 prefixes just suppressed from BGP Updates? Does the BGP neighbor relationship take a hit (similar to exceeding the inbound prefix limit)?
How are others designing around this limitation in situations where the customer has > 20 VPC attachments?
When a customer associates a Transit Gateway to Direct Connect Gateway, customer provides a list of prefixes which are advertised to on-prem and this is where limits are enforced. If customer needs to add or delete the routes advertised, they can use the "UpdateDirectConnectGatewayAssociation" API to change it.
My general advice to customers is to summarize as much as possible and use contiguous blocks for their cloud footprint holistically.
Relevant questions
Can we form AWS Transit Gateway attachments using <1Gbps hosted DX?
Accepted Answerasked 3 years agoAWS Direct Connect route limit
Accepted Answerasked 3 months agoMigration from Transit VPC to AWS Transit Gateway
Accepted Answerasked 2 years agoTransit Gateway - number of prefixes from TGW->CGW
Accepted Answerasked 3 years agoConnect remote sites using VPN to access on-prem via existing Direct Connect?
Accepted Answerasked 2 months agoTransit Gateway Direct Connect Gateway allowed prefix interactions
Accepted Answerasked 2 years agoTransit Gateway to Direct Connect Gateway to Transit Gateway
Accepted Answerasked 2 years agoTransit Gateway and SD-WAN
Accepted Answerasked 3 years agoSummarize Transit Gateway Prefixes across Multiple TGW
Accepted Answerasked a year agoTransit Gateway attachment cost to VPC and subnets
Accepted Answerasked 2 years ago