[187979] in North American Network Operators' Group
Re: AWS Direct Connect - Peering VPCs to Tier 1's and MPLS
daemon@ATHENA.MIT.EDU (George Herbert)
Tue Mar 1 14:26:01 2016
X-Original-To: nanog@nanog.org
From: George Herbert <george.herbert@gmail.com>
In-Reply-To: <505999303.21820.1456852610435.JavaMail.zimbra@baylink.com>
Date: Tue, 1 Mar 2016 11:25:59 -0800
To: "Jay R. Ashworth" <jra@baylink.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
If you're asking if one can get a provider's router to handle the outside ph=
ysical part of a DC connection... As an ISP service so you don't need your o=
wn router hardware...
I was working on this for a recent ex client and asked Level 3 exactly that q=
uestion. I believe I had the right network guy on the phone and it was a fi=
rm no.
I was going to check all the other Direct Connect providers but client ran o=
ut of $$.
If anyone does do that, I would like to know and pass it along to ex client f=
or their information.
George William Herbert
Sent from my iPhone
> On Mar 1, 2016, at 9:16 AM, "Jay R. Ashworth" <jra@baylink.com> wrote:
>=20
> 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...
>=20
> 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 a=
nd
> MPLS; is there a "native" way to do that from an AWS VPC instead?
>=20
> Any public or private replies cheerfully accepted; will summarize what I
> can to the list.
>=20
> Cheers,
> -- jra
>=20
> --=20
> Jay R. Ashworth Baylink jra@baylink=
.com
> Designer The Things I Think RFC 2=
100
> Ashworth & Associates http://www.bcp38.info 2000 Land Rover=
DII
> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1=
274
