[AusNOG] AWS DirectConnect billing

Gavin Tweedie gavin.tweedie at megaport.com
Fri Jul 9 15:55:33 EST 2021 

Hi Rhys,

Megaport provides connectivity under both a Hosted VIF or a Hosted
Connection model with AWS.

Long and the short of it: you can request the VXC to be spun up without
needing anything more than the end customer’s AWS account ID (numeric
value). Either of the above connection types will end up as an inbound
connection request automatically on the end customer’s AWS console for them
to accept.

Hosted VIF:

   - VXC Configurable between 1 Mbps - 5 Gbps
   - AWS Private or Public peer types supported (basically IaaS or PaaS)
   - AWS port hourly fee is not levied to the end customer
   - Ability to change the VXC speed
   - Managed and monitored share
   - Inputs needed: AWS account ID and customer side ASN (private or public)
   - IP addressing can be specified at circuit creation time, mandatory for
   public only

Hosted Connection:

   - AWS Port fee is billed through Amazon
   - Set VXC speeds increments from 50 Mbps to 10 Gbps
   - Dedicated 1:1 bandwidth
   - VXC speed changes not supported once provisioned
   - Support for AWS Private or Public peer types at all bandwidths
   - Support for AWS Transit VIF (to use Transit Gateway) at 1 Gbps or above
   - Support for diverse ports for resiliency (at single DC)
   - Inputs needed: Only AWS account ID required at circuit creation time

Documentation and guidance at: https://docs.megaport.com/cloud/megaport/aws/
AWS port hourly fees are detailed at:
https://aws.amazon.com/directconnect/pricing/

Megaport fees are calculated by A/B endpoints in the portal. In general for
Hosted VIF the costs would be the standard metro flat rates between
1-1000Mbps and 1G-10G. There is an additional cost element to the Hosted
Connection product on the Megaport side which is calculated per Mbps for
the 1:1 assigned nature of the traffic.

Reach out to sales at megaport.com or your account manager for more info.

Cheers
Gavin

On Fri, Jul 9, 2021 at 1:06 PM Nick Pratley <nick at npratley.net> wrote:

> Hey Rhys,
>
> You are correct in all cases.
>
> 1. You pay for a port and the VLL / VXC
> 2. Provider hands you the service as a VLAN on your port
> 2. Your customer pays AWS hosted port rate and the outbound traffic rate.
> 3. You do not need an AWS account.
>
> When ordering the service, you'll provide your customers Amazon Account
> Number. With this, your partner orders the service to that AWS Account, and
> your customer gets a request to approve.
>
> For IX Australia, we don't charge for the first 5 VLLs per port within the
> same exchange :-)
>
> Kind Regards,
> *Nick Pratley*
> P: 0448 379 418
> E: nick at npratley.net
>
>
>
> On Fri, Jul 9, 2021 at 3:00 PM Rhys Hanrahan <rhys at nexusone.com.au> wrote:
>
>> Hi Guys,
>>
>>
>>
>> I have a customer who might be interested in a DirectConnect private VIF.
>> I have talked to an AWS partner about their costs (Port + Virtual Circuit
>> cost) but I’m a bit fuzzy on how the billing works on the AWS side (i.e.
>> who gets billed us or them?). Can anyone confirm if I have this breakdown
>> right? I’ve looked at doing a public VIF ourselves in the past but unclear
>> on the private VIFs.
>>
>>
>>
>> Also – I am looking to push DirectConnect as a more reliable solution
>> because the existing IPSec tunnel keeps droping out (I assume DirectConnect
>> is a private VLAN so is it considered acceptable to not encrypt the BGP
>> session generally?). If anyone has any anecdotes that confirm DirectConnect
>> being more reliable/performing better/lower latency, that would be much
>> appreciated! I’d love to be able to solidly say that Direct Connect will be
>> a better experience.
>>
>>
>>
>> My understanding, based on: https://aws.amazon.com/directconnect/pricing/
>> and https://docs.megaport.com/cloud/megaport/aws/hosted-vif/
>>
>>    - We pay a partner for a port
>>    - We pay a partner for a VXC connection that links to a particular
>>    AWS account (I assume this links to the end customer’s AWS account – not
>>    ours?)
>>    - The VXC gets handed off to us as a VLAN on our side that we can
>>    then hand off to a CPE, and shows as a private VIF on customer’s AWS
>>    account.
>>
>> Then:
>>
>>    - The end customer pays the hosted connection “port” rate on their
>>    AWS account (so we don’t get charged this?)
>>    - The end customer pays the data transfer outbound pricing per GB on
>>    their account (so we don’t get charged this?)
>>    - The VIF gets linked to the customer’s Virtual Private Gateway and
>>    we can setup a BGP session between the two endpoints.
>>
>>
>>
>> So if I am understanding right, we don’t even really need an AWS account
>> ourselves to deliver this service via a partner? Unfortunately getting firm
>> answers on the AWS side of things from the partner has been tricky.
>> Appreciate any guidance – if anyone knows Megaport or IX Australia’s
>> pricing for this kind of thing that would be great too as I’m looking at my
>> options.
>>
>>
>> Thanks everyone! Happy Friday.
>>
>>
>> *Rhys Hanrahan* | Chief Information Officer
>> *e:* *rhys at nexusone.com.au <rhys at nexusone.com.au>*
>>
>> [image: www.nexusone.com.au] <http://www.nexusone.com.au/>
>>
>> *NEXUS ONE*
>> *p:* 1800 NEXUS1 (1800 639 871) *|* *a:* Suite 12.03 Level 12, 227
>> Elizabeth Street, Sydney NSW 2000
>> *www.nexusone.com.au <http://www.nexusone.com.au>*
>>
>> *The information in this email and any accompanying attachments may
>> contain; a. Confidential information of Nexus One Pty Ltd or third parties;
>> b. Legally privileged information of Nexus One Pty Ltd or third parties;
>> and or c. Copyright material Nexus One Pty Ltd or third parties. If you
>> have received this email in error, please notify the sender immediately and
>> delete this message. Nexus One Pty Ltd does not accept any responsibility
>> for loss or damage arising from the use or distribution of this email.*
>>
>> *Please consider the environment before printing this email.*
>> _______________________________________________
>> 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
>


-- 
Global Interconnection Director
Megaport <https://www.megaport.com>
+61 424 229 127
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20210709/303e16ed/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 13832 bytes
Desc: not available
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20210709/303e16ed/attachment-0001.png>

More information about the AusNOG mailing list