News for hackers. Stuff that matters.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by minhazm on Monday April 12, 2021 @12:46PM (#26781666)
Is it really price gouging for bandwidth? Or is bandwidth just really expensive in general? I honestly don't know. I would assume if it was actually much cheaper one of the cloud's would undercut the other to get customers.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by TechBro8615 on Monday April 12, 2021 @12:56PM (#26781825)
It's absolutely price gouging. I'm not going to rant about this for the 100th time, but at least I'm in good company [0]. Do the math on the cost you pay if you saturate 1gbps for a month vs. the cost you pay for 1gbps IP transit at basically any colocation provider.

Really this is the secret sauce of the cloud. Create new abstraction layers where you can charge for logical separation on a physical basis. First VMs, then containers, then serverless... Would be cool if somebody did it with bandwidth (looking at you, Cloudflare). Why can't I buy an elastically sized pipe? Why do I need to pay for the stuff I put through it instead of reserving a size for the time I'll need it?

[0] https://twitter.com/eastdakota/status/1371252709836263425

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by sofixa on Monday April 12, 2021 @04:26PM (#26784700)
That Twitter thread is only including pure bandwidth. What about all the highly redundant networking equipment ( firewalls, routers, switches, Nitro offloading, DDoS protection, attack detection), software for all those abstractions you get ( VPCs, subnets, security groups, vpc peerings, Elastic IPs etc. ) and engineers? None of what i listed you pay for directly, and bandwidth seems to be the most reasonable product to lump it all in.

It's like going to a restaurant and complaining about the price of steaks because beef should cost a lot less. There's a ton of other things involved, and yes, they probably have a decent margin, but not as much as you initially imply.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by pas on Monday April 12, 2021 @08:46PM (#26786949)
AWS has advantage due to economies of scale. (And naturally some disadvantages and challenges due to sheer size, which increases fixed costs, but that means that they can't easily downsize, which doesn't apply since they are still growing at an incredible rate.)

So they should be able to reach the lowest amortized cost for bandwidth with all of those costs included.

They price bandwidth so high because they can and they are still growing.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by maximente on Monday April 12, 2021 @01:31PM (#26782373)
boy howdy, with all the flak i hear about this and the awesome talent in tech, you'd figure an entrepreneur or 1000 would take a stab at this, make it better, charge less. apparently there's gazillions to be made by even charging 50 percent of what AWS does.

so, when should we expect this gloriously efficient competitive market to kick in to action?

my guess is that the AWS ecosystem, despite "price gouging", is simply the best and will be because this is really hard, non-glorious engineering, where solid reliability actually matters. anyone who wants to can go ahead and co-lo, so, whatever. people who want cloud will pay, and those who can't or won't, will not.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by toast0 on Monday April 12, 2021 @02:09PM (#26782889)
There's tons of businesses that are happy to charge less for bandwidth; so it's clear Amazon (and some of the other high tier cloud services) are overcharging on this maybe by a factor of 10, although since transit bits are not all equal, someone with more detail could make a case that the overcharging is less.

It's easyish to compete on bandwidth costs, but Amazon has a lot of other features many people want; it's harder to replicate all of those, especially the part about having a long history of operating such services and not making a lot of changes to make things more expensive or otherwise more difficult. Having to pay a much higher than market price for an easily replaced good in order to get a good that's less easily replaced is textbook anti-competive bundling.

If your bandwidth usage is high enough, maybe it makes sense to send it all through AWS direct connect, and pay for transit yourself; although even then, the AWS direct pricing seems a bit high.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by VectorLock on Monday April 12, 2021 @03:38PM (#26784125)
This is like going to a fancy restaurant and being upset that they charge so much for a steak when you can get beef at the supermarket for much less.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by pas on Monday April 12, 2021 @08:51PM (#26786994)
No, it's complaining that the water at the fancy restaurant is priced expensively, but people still go there because the many options for food.

And it's easy to replicate the water part (after all VPS providers are dime a dozen), the hard part is the food.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by stefan_ on Monday April 12, 2021 @04:35PM (#26784825)
If you ask the fancy restaurant to cater a steak dinner for 1000 people they will charge you a lot closer to supermarket beef.

The point is that if you charge absurd prices for what has basically no marginal cost your pricing model is broken and 1) you are excluding customers that are particularly sensitive to this price or 2) you are liable to undercharge other customers that primarily use other services for which you are not charging what it costs you to provide.

For AWS, given the generally inflated prices, it's probably a lot more of 1) than 2).

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by VectorLock on Monday April 12, 2021 @04:57PM (#26785078)
As I explained in another commented AWS wants to disincentivize dumb bandwidth usage. They want you to use your bandwidth for traffic that needs it to EC2, and you get much better rates for static data from CDNs, S3, etc.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by lostcolony on Monday April 12, 2021 @01:46PM (#26782561)
Your point that "AWS has a bunch of other benefits to where people just accept the bandwidth costs so they can leverage those other benefits" doesn't actually counter the original claim that "the bandwidth costs are outrageously overpriced".
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by manigandham on Monday April 12, 2021 @03:24PM (#26783930)
You're replying to a comment that includes a tweet from the CEO of Cloudflare, which is quite literally providing that competition with free bandwidth and an increasing suite of computing products.

There are plenty of other platforms as well, like Digitalocean, that have much lower bandwidth pricing.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by Dylan16807 on Monday April 12, 2021 @01:45PM (#26782550)
What competitive market?

Nobody else can give you bandwidth out of Amazon data centers. Amazon's advantage is having a ton of services that work together, and they take advantage of it to price gouge on bandwidth.

If you're buying a standalone CDN service you can get massively better rates.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by ikiris on Monday April 12, 2021 @08:14PM (#26786700)
You're free to go build your own cloud and sell it for cheaper. I'll wait.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by VectorLock on Monday April 12, 2021 @03:37PM (#26784105)
I'm kind of surprised that people are this upset about how much AWS charges for bandwidth. They may charge more for bandwidth than a colo would but they're not a colo. A colo you get a network port and -thats it- you provide everything else yourself, with its attendant cost, and you roll that up into your total bill.

If a colo provides you a 1 Gbps connection if you use less, you don't get a refund. And most of the time you don't get 24/7 saturation, or you get charged on some 95th percentile billing, and their networks are almost always oversubscribed anyways.

AWS is trying to disincentivize using it as a dumb pipe. They want you to use it smartly and if you just want to push static data there are much more cost effective ways to do it, such as CDNs, which are more cost effective for both you AND AWS.

Comparing AWS bandwidth costs and Colo and even other clouds like Oracle isn't fair because different things are associated with that cost.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by GordonS on Monday April 12, 2021 @01:33PM (#26782398)
It really is price gouging - bandwidth is actually cheap.

A couple of comparisons:

Oracle Cloud give you 10TB of bandwidth for free, with overage charged at around €7.5/TB.

You can rent a VPS from the likes of Hetzner, and they will throw in 2-20TB of bandwidth for free, with overage charged at something like €1/TB - AWS charge an eye-watering €125 for each TB!

I think the reason the big 3 (AWS, Azure, GCP) still charge such huge amounts is that they profit so greatly from it, and there is more than enough business to go round.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by veeti on Monday April 12, 2021 @02:23PM (#26783093)
You know you're greedy when Oracle is cheaper
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by sofixa on Monday April 12, 2021 @05:18PM (#26785325)
> I think the reason the big 3 (AWS, Azure, GCP) still charge such huge amounts is that they profit so greatly from it, and there is more than enough business to go round

Or that their networking does vastly more and is of better quality? Hetzner can't provide you with everything around a VPC that AWS do. Just a tiny example - peering VPCs across regions, which is free.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by rodgerd on Monday April 12, 2021 @06:10PM (#26785803)
I would say that it's two simple factors:

1. High bandwidth charges are an effective form of lock-in. Once your data is there, it's prohibitive to move it out again.

2. Bandwidth use is very poorly understood in many businesses, compared with simpler metrics like storage, memory, and CPU. AWS can run razor-thin margins on things that people easily compare to on-prem or VPS-style offerings, and then make the money back in areas like network traffic, fine-grained monitoring, and other items that as less obvious.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by martinald on Monday April 12, 2021 @01:42PM (#26782489)
I totally agree, but was stunned to see DigitalOcean charging $0.10/GB for outbound transfer for their new (quite cool imo) apps service. You do get 40GB-100GB included, but it means it's unusable for bandwidth heavy apps. They include 1TB (which is pooled across all VMs) and 0.01/GB on their standard platform.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by GordonS on Monday April 12, 2021 @01:56PM (#26782710)
Yeah, I think Digital Ocean are really taking the piss there - proven by their existing $0.01/GB pricing, as you mentioned.

I reckon DO have seen the big providers getting away with it, and they want a piece. Why wouldn't they, when there is apparently so little pushback?

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by martinald on Monday April 12, 2021 @05:19PM (#26785336)
I suppose you have object storage which is still $0.01/GB (plus includes 1TB to start with), so for most apps your bandwidth will come out of that for most files, so your 0.1/GB price is only for html/api/etc transfer. But still, it's annoying and seems completely arbitatary.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by arkitaip on Monday April 12, 2021 @12:51PM (#26781745)
Why would players in an oligopoly undercut each other when their implicit agreement around pricing makes all of them richer? Also, second tier cloud providers like Oracle give deep discounts and still can't compete with AWAZGO so pricing isn't necessarily a main competitive advantage.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by kmeisthax on Monday April 12, 2021 @02:27PM (#26783145)
Oracle's problem is that nobody wants to work with Oracle. If I was managing a high-bandwidth service I would avoid Oracle Cloud purely to avoid legal risk to my clients.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by DetroitThrow on Monday April 12, 2021 @05:24PM (#26785390)
While I agree that's why no one uses Oracle, corps not competing for price at the tier 1 provider level still isn't great for the consumer/market, which is what I think the original commenter was getting at.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by stefan_ on Monday April 12, 2021 @03:03PM (#26783639)
Keep in mind bandwidth gets cheaper as AWS gets bigger. If you are some random tiny colo provider, people don't necessarily care to peer with you unless you pay them for the privilege. If you are originating 20% of internet traffic, now people need to peer with you or their customers won't have a great experience.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by gatvol on Monday April 12, 2021 @03:29PM (#26783983)
If you think AWS is expensive, give AZURE a go and be appalled.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by gnfargbl on Monday April 12, 2021 @02:30PM (#26783198)
IP transit costs something like $350-$700/mo for a Gbit. Amazon are certainly getting better rates, so even with equipment costs I doubt they're spending much more than $0.005/GiB. Their pricing starts at $0.15/GiB. (Not to single out AWS, the other big providers are much the same.)
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by ev1 on Monday April 12, 2021 @03:58PM (#26784371)
I'm below $100/1Gbps 95% with more than one provider as a small player
Re:OpenSearch: AWS fork of Elasticsearch and Kibana by gnfargbl on Monday April 12, 2021 @04:28PM (#26784735)
That's sounds like a great deal: you're paying less than half of Hurricane's advertised minimum price. And I had understood HE were a mid/low price carrier.

Can I ask, are you in a data center? US or Europe?

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by ev1 on Monday April 12, 2021 @04:42PM (#26784886)
What do you mean? Hurricane's current special is $90/1Gbit/m.

US.

Some of the larger bandwidth transit resellers like FDC will do Cogent for $0.02/Mbps. They have a marketing site at epyc100gig.net (not an affiliate or employee; just a FDC customer).

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by gnfargbl on Monday April 12, 2021 @04:50PM (#26784999)
OK, either I'm getting pretty screwed somewhere or EU prices are well above the US. Probably the former. Thanks for the pointer.

https://he.net/cgi-bin/ip_transit_quote is where I'm seeing the $200 number.

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by ev1 on Monday April 12, 2021 @04:51PM (#26785006)
On front page https://www.he.net/ there's a special in the top right :)

I believe that kind of low-for-1G-commit pricing is for their fully owned FMT1/FMT2 US CA facility. You have a lot easier peering in EU (AMSIX, DECIX, etc) that will help compared to the US's love of commercial exchanges like Any2/Coresite/Equinix where peering costs practically more than transit.