[AusNOG] Bgp capable router for aws direct connect

Bill Walker bill at wjw.co.nz
Wed Oct 8 14:01:27 EST 2014


Cameron is correct, it's one BGP session per VPC, if you want everything 
to be private. Otherwise you can setup peering between VPC's but the VPC 
peering traffic costs $$$$ so you will be paying twice for that traffic.


On 2014-10-07 23:24, Cameron Daniel wrote:
> On 2014-10-07 6:50 pm, Matthew VK3EVL wrote:
>> Keeping it simple. One side, aws, will only feed routes via bgp. It
>> will have 50 or so private ip /21s
>> Default route on the other interface going to the core that is more
>> than capable of gigabit but not licensed for bgp. Any filtering will
>> be done there or on a firewall.
> 
> Be aware that if those 50 or so prefixes will be from 50 or so VPCs
> then I think you'll need that many BGP sessions as well. This might
> also be a limit if you're looking at a switch to handle the routing.
> 
> If it's a public virtual interface for non-EC2 AWS services then 
> disregard
> 
> Cheers
> Cameron
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog


More information about the AusNOG mailing list