[187982] in North American Network Operators' Group
Re: AWS Direct Connect - Peering VPCs to Tier 1's and MPLS
daemon@ATHENA.MIT.EDU (Michael O'Connor)
Tue Mar 1 15:41:42 2016
X-Original-To: nanog@nanog.org
In-Reply-To: <505999303.21820.1456852610435.JavaMail.zimbra@baylink.com>
Date: Tue, 1 Mar 2016 15:41:35 -0500
From: "Michael O'Connor" <moc@es.net>
To: "Jay R. Ashworth" <jra@baylink.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Jay,
VPC is supported over IPsec if your public path is sufficient into the AWS
cloud.
AWS shortens DirectConnect to DX not DC for some reason.
The AWS DirectConnect service is built on 10G infrastructure so using
potentially larger interconnects over public peerings with IPsec could be
advantageous.
DX requires fiber cross connects in addition to any other AWS peerings that
you may have at a particular location.
-Mike O'Connor
On Tue, Mar 1, 2016 at 12:16 PM, Jay R. Ashworth <jra@baylink.com> wrote:
> Just got this dropped on my desk an hour ago, and I'm not finding as much
> material online as I might have hoped for...
>
> It looks like the easiest solution is to just hang a router/firewall at
> Equinix Ashburn and AWS-DC to that, and then peer it to carriers both IP
> and
> MPLS; is there a "native" way to do that from an AWS VPC instead?
>
> Any public or private replies cheerfully accepted; will summarize what I
> can to the list.
>
> Cheers,
> -- jra
>
> --
> Jay R. Ashworth Baylink
> jra@baylink.com
> Designer The Things I Think RFC
> 2100
> Ashworth & Associates http://www.bcp38.info 2000 Land
> Rover DII
> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647
> 1274
>
--
Michael O'Connor
ESnet Network Engineering
moc@es.net
631 344-7410
