Just to clarify, AWS has a feature called PrivateLink [1] that charges $.01/GB transferred between a Service provider and the end customer (I thought there was a free variant for same AZ, but I seem to be wrong about that).
We offer a similar feature called VPC Peering, and in particular Private Service Access [2]. Because we can be sure that the traffic is in the same Zone (or not), talking to a third-party service in the same Zone does not incur egress charges.
But did you mean this $.01/GB or were you thinking of VM <=> Internet / External IP pricing?
Generally a VM <> external pricing.
Its tricky to setup Privatelink with a service provider. For example Elastic cloud will have its own kubernetes setup. It could be behind a HW loadbalancer - how do you set up Privatelink there ?
Super tricky and not applicable in all circumstances. GCP and AWS must move towards sane traffic pricing (or risk anti-monopoly lawsuits). The licensing changes are just a first step.
P.S. : offtopic... can i use privatelink between AWS and Google Cloud ? do you have an idea on how much it would cost on either side ?
> can i use privatelink between AWS and Google Cloud ? do you have an idea on how much it would cost on either side ?
You basically have to hookup Cloud Provider A through a middle layer to Cloud Provider B (e.g., connect via Equinix or Megaport). It’s not drastically different than a hybrid setup, except you don’t control the premises on either side.
While getting you the right link to our Partner Interconnect docs, it turns out we have a nice solution guide writing up the various options [1].
The costs boil down to some non-trivial fixed price each month to cover the 1/10/100+ Gbps connection on each side, plus whatever transfer fees each provider charges for egress over that method. At large enough volumes, providers of all sorts usually have equivalent fixed prices. Getting multiple redundant lines, or doing VPN encryption, obviously costs more and is more work than “just a pipe”.
Even at list prices though, this gets you closer to $.02/GB each way in Europe or North America. At high volume in the same metro area (like Northern Virginia), you can easily agree to much lower rates on either side.
I don't think it would be hard to offer PrivateLink to tenants via Kubernetes. You'd just make a K8s LoadBalancer, set the annotations to back it with an NLB, then expose that with PrivateLink.
> If the VPCs in the VPC peering connection are within the same region, the charges for transferring data within the VPC peering connection are the same as the charges for transferring data across Availability Zones. If the VPCs are in different regions, inter-region data transfer costs apply.
I checked with a couple of people and they read the above to mean that any peering data transfer costs the SAME as if you were transferring data across availability zones. This is not free.
Well sure, it's not free, but it's the same cost as if you were moving data within your AWS account, so they're not charging for the use of VPC peering specifically.
Just to clarify, AWS has a feature called PrivateLink [1] that charges $.01/GB transferred between a Service provider and the end customer (I thought there was a free variant for same AZ, but I seem to be wrong about that).
We offer a similar feature called VPC Peering, and in particular Private Service Access [2]. Because we can be sure that the traffic is in the same Zone (or not), talking to a third-party service in the same Zone does not incur egress charges.
But did you mean this $.01/GB or were you thinking of VM <=> Internet / External IP pricing?
[1] https://aws.amazon.com/privatelink/
[2] https://cloud.google.com/vpc/docs/configure-private-services...