[AusNOG] AWS Direct Connect

[Matthew Horvat]

Hi Skeeve

To add to what Bill Said

The benefits on the Megaport VXC virtual direct connect are the ability to scale the speed down to 100mbps whereas the straight direct connect is a fixed 10Gbps or 1Gbps

Also I'm not sure if they have enabled the feature yet, but they will be able to only charge on usage on both the Megaport and AWS side as opposed to the hourly usage charge.

Matt

Matthew Horvat
Systems Engineer
Technical Solution Delivery Team
Tel: +61(2) 9008 2338 matthew.horvat at aseit.com.au 


 
www.aseit.com.au
 
Sydney | Melbourne | San Francisco | New York | London



This email is sent on behalf of ASE IT or one of its group companies in the territory from where this email has been sent, it is only for the person or entity that is the inteneded addressee and may contain confidential or privileged information. If you are not the intended recipient of the email, any use, interference with, disclosure or copying of this email is unauthorised. If you have received this email in error, please delete it and notify me promptly. Thank you



-----Original Message-----
From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Bill Walker
Sent: Tuesday, 8 July 2014 6:59 AM
To: ausnog at lists.ausnog.net
Subject: Re: [AusNOG] AWS Direct Connect

Hi Skeeve,

We have a AWS Direct Connect via Megaport VxC in Sydney and a X-Connected Direct Connect in Chicago. With the VxC you only get one interface on the AWS side, as we need access to both the public and private side of AWS, we have a Public Interconnect with BGP Peering into AWS, then we run an IPSec Tunnel over the top to hook into our VPC's. If I was a service provider I would be purchasing a X-Connect.

Also I had a long chat with an Amazon Solutions Architect about redundancy and the current supported options are either:

a) 2 x Direct Connects with a private VLAN over each
b) 2 x IPSec Tunnels over the public internet/public peering

We opted to keep the same model everywhere, so we use IPSec tunnels over public peering. The idea being that if we lose L2 connectivity, the BGP session will drop and Amazon's prefixes from one of our other IP Transits will take precedence.

I have the kids today so this is a bit of a ramble, but feel free to call if you want a chat +64 21 241 7206

Cheers,

Bill


On 2014-07-08 03:34, Skeeve Stevens wrote:
> Hi,
> 
> I wanted to understand if there is any functional/technical difference 
> between AWS Direct Connect via direct X-Connect or via Megaport VxC?
> 
> Also, does anyone know the costs of AWS DC via X-Connect?
> 
> ...Skeeve
> 
> SKEEVE STEVENS - eintellego Networks Pty Ltd
> 
> skeeve at eintellegonetworks.com ; www.eintellegonetworks.com [1]
> 
>  Phone: 1300 239 038; Cell +61 (0)414 753 383 ; skype://skeeve
> 
> facebook.com/eintellegonetworks [2] ;  [3]linkedin.com/in/skeeve [4]
> 
> twitter.com/theispguy [5] ; blog: www.theispguy.com [6]
> 
> The Experts Who The Experts Call
> Juniper - Cisco - Cloud - Consulting - IPv4 Brokering
> 
> Links:
> ------
> [1] http://www.eintellegonetworks.com/
> [2] http://facebook.com/eintellegonetworks
> [3] http://twitter.com/networkceoau
> [4] http://linkedin.com/in/skeeve
> [5] http://twitter.com/theispguy
> [6] http://www.theispguy.com/
> 
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog