Vpc Peering Bandwidth Limits

Aws publishes vpc limits at this link.

Vpc peering bandwidth limits. Vpc peering has no aggregate bandwidth individual instance network performance limits and flow limits 10 gbps within a placement group and 5 gbps otherwise apply to both options. The traffic between virtual machines in peered virtual networks is routed directly through the microsoft backbone infrastructure not through a gateway or over the public internet. In addition to limits there are limitations in functionality.

This is a hard value. A given vpc network can peer with multiple vpc networks but there is a limit. For example an aws vgw carries a hard limit of 100 bgp routes in total.

There isn t any additional restriction on bandwidth within the peering. Maximum bandwidth burst per vpc direct connect gateway or peered transit gateway connection. The number of entries per route table should be increased accordingly.

With transit gateway maximum bandwidth burst per availability zone per vpc connection is 50 gbps. Default subnets within a default vpc are assigned 20 netblocks within the vpc cidr range. Default vpcs are assigned a cidr range of 172 31 0 0 16.

50 gbps maximum bandwidth per vpn tunnel. To request a vpc peering connection with a vpc of another tenant the peer tenant must accept the request to activate the connection. When the bgp prefixes exceed 100 vgw randomly resets the bgp session leading to unpredictable potential network downtime.

A rule that specifies source ranges of 10 100 0 1 32 and 10 100 1 1 32 and destination protocols and ports of tcp 80 tcp 443 udp 4000 5000 and icmp count as nine one each for the two ip. Only vpc peering supports placement groups.