AWS price reduction for data transfers out to the internet
aws.amazon.com
aws.amazon.com
Third party SaaS offerings that move large amounts of data are effectively forced to host in AWS.
Want a small number of high-value servers (e.g. big GPUs, etc) in your own data center or colo to use for non-availability-critical purposes integrated with the rest of your AWS stack? You’d better price in egress!
Want to gradually transition to a competing cloud? Good luck, egress will bankrupt you before you finish the transition.
As for everything else, AWS offers tiered pricing for everyone and it's the same for everyone. They just don't publish the tiers at that level, but yes, Netflix pays less than you probably do because they're in the higher tier -- but they pay the same as all the other companies at that tier.
They do offer the Snowball to lower transfer out cost, they also offer Direct Connect which is more convenient and can be cheaper.
For sure it won't be cheap, but being able to transfer 100 TB for less than 3k isn't too bad. Storing that on S3 would cost you nearly that per month... if you can't spare a month of cost to migrate, you may want to rethink your pricing.
They do for both Snowball and Direct Connect, but it's 2 cents per GB, which is what I used to give the 3k estimate.
I've seen some of the inner workings of the big cloud providers' networking stacks. The networking infrastructure, the software that runs it, the software that exposes it to customers, the thousands of engineers working at any given moment in AWS/GCP/Azure's NOCs to maintain uptime are truly some of the most impressive technical marvels I have ever seen. They aren't as sexy to discuss on HN as something like the managed containers services, functions as a service, EC2 etc, but the networking stacks like the VPC, NAT gateways, subnet routing, privatelinks, security groups, ENIs, nitro cards, etc are pure magic as far as I'm concerned and are so so so much more complicated than a standard data center's networking stack, or even Cloudflare's stack.
To use Cloudflare's "bucket of water" metaphor, AWS isn't even close to just being a dumb bucket of water that you fill with water and then get charged to take out the water. There is so much that happens inside of that bucket to segment your water into different pipes, routing your water in all kinds of customer-customizable ways for many different use cases, mixing/heating/cooling your water as you need, all while guaranteeing things like making sure your water arrives exactly where it is supposed to arrive and doesn't get contaminated or leaked along the way.
Does AWS make a big markup on bandwidth? Yea, surely they do. But is it as simple as Cloudflare says it is? Not even close.
Recently I've been working with https://fly.io/ for a new app and it's a breath of fresh air compared to working with the big cloud providers. They offer simple but robust networking primitives built on top of ipv6 and WireGuard and provide a ton of value add on top like global distribution & load balancing, service discovery, TLS termination, all of which just work exactly like I'd expect it to, out of the box without any configuration on my side.
EDIT: Almost forgot to mention: their egress costs are also much more reasonable: https://fly.io/docs/about/pricing/#outbound-data-transfer
If its Linode style - delayed status page updates - sometimes as much as 15minutes, zero detail post-mortems - this problem has been fixed by our engineers thank you yada yada, and same issues repeat six months down the line then I will be understandably disappointed.
You can see them responding to customers and providing updates in real time here: https://community.fly.io/t/there-seems-to-be-an-outage-with-...
And a detailed postmortem here: https://community.fly.io/t/major-outage-portmortem-2021-10-1...
They also update their status page pretty diligently whenever something goes wrong even for things that don't necessarily impact all customers (the only recent item on there that affected my app directly was the Oct 13 one from what I can remember): https://status.flyio.net/history
It’s simply obvious that it’s not a good deal if you’re not their target customer with a use case they cater to. However, it could be a good deal if you have a relevant use case. Unless it’s being suggested that AWS caters to everyone in all cases then it adds nothing to the conversation to point it out.
Being lynched for egregious egress fees is only something I've experienced when using mega corp's clouds, where economies of scale suggests their vastly larger size should allow them to provide even better value.
But that's in a normal market, not the artificial lock-in mega cloud corps enjoy where they're able to distort customer behavior from artificially high pricing.
I don't think I've seen a latency spike on AWS in 10 years. Hetzner, it's often possible to observe latency and drops over 10 minutes (and the situation hasn't changed much in about 10 years)
The primary issue I have with them is latency access to their DE/FI data centers from the US, if their US DC offered dedicated servers I would be migrating to over to use them instead.
If you haven't experienced Google translating insistently German responses from one of their DC techs you probably haven't been using them for long enough ;)
As for networking, would encourage installing something like Smokeping
But I don't really access AWS support either, when something doesn't work I've just killed the VM and started a new one. It's less disposable with bare metal servers, I can physically restart the server from their control panel or if issues are not fixable, reset the server with a new Linux OS image, which granted would be a lot more time consuming.
I will add that whilst I'm not in the business of dictating which cloud services business customers would use, I'd agree that I would recommend AWS over Hetzner who are a) paying for & would have to administer it themselves and b) is going to have access to all the managed services they would ever need in future.
I would still recommend they consider Hetzner for any high-resources intensive workloads where their raw compute is vastly less expensive. I'll also chose the cheaper reoccurring cost over convenience when I'm able to self-service it myself.
All of the other networking stuff ( Security Groups, NACLs, flow logs, VPCs, subnets, etc.) you don't directly pay for, isn't magic either, but also cost money.
The ASICs are on the fabric doing the routing and NAT for all the traffic in the AZ. These ASIC are unlikely to be custom. Hyperscale operators typically use open networking hardware with merchant silicon. You can get open networking hardware to do all sorts of packet manipulation, and these devices are a cheaper than traditional manufacturers, but more powerful as they expose more low-level interfaces.
All those features you talk about are implemented from features that are provided by these hardware platforms.
AWS is just putting an managed service together from them, no different to how they take postgres, do some tweaks and rebrand it as an AWS service.
Those are separate charges from the EC2 costs the Cloudflare blog post discussed.
Raw pipe isn’t priced in GB it’s in capacity. To serve GB on Black Friday you need to provision far far more capacity
Cloudflare used a 5x multiplier. How high do you think it needs to be? Does total AWS bandwidth even go up that much on black friday?
SaaS and cloud providers in particular have a lot of leverage over their customers due to the typically high cost of switching. E.g. what does it cost to move your whole infrastructure to a new cloud? They can basically gouge you up to that cost threshold.
These cost of switching actually leads to a market that is not competitive in the traditional sense. Yes, competition on the surface, but monopoly within.
It's true that gouging can't be as egregious as a true monopoly environment, but certainly much higher than a low cost of switching environment.
The big tell is margins. Anytime a company can sustain excessively high margins, it's usually a tell that theres a lack of a competitive market. A lot of software companies get high margins either by being first to market (by many years), or leveraging high cost of switching.
Despite software being cheap to deliver, it's also cheap for your competitors to deliver, so margins should be low in a highly competitive market, regardless of marginal cost of production.
I do believe new regulation is needed to handle these business models such that we can continue to foster a competitive environment. It would have to be very carefully crafted to prevent unintended second order effects of course.
So instead of using the cheapest vendor, companies use AWS for a ton of reasons (broad support, everyone knows how to work with it so it makes recruiting easier, hundreds of features, etc...) and their high bandwidth bill is worth it.
The egress is a way to snare a lot of extra margin.
It's 100% clear that orgs. wanting to host large public platforms will have 'major concerns' over this pricing issue but that's not their target market.
I'll bet most HNeers are thinking in terms of 'Hosting my App' there vs. AWS Bread and Butter is mostly hosting corporate IT services, which is a different thing.
https://www.nytimes.com/2020/10/25/technology/apple-google-s...
I mean the politicians are in on it, and turn against them when their ability to control elections for their own purposes comes into question.
Look at the “testimony” of Robinhood guy. It’s a scripted TV show; you lose.
> Restaurants and bars have around a 70% profit margin on a bottle of soda and soft drink, while retailers typically have between 30–50%.
Theatres make 0% margin on the Ticket and probably 90% on the soda and popocorn.
The analogy is reasonable: 'The Food' , 'The Film' or 'The EC2's are the primary ticket item and it's ballpark competitive on a cost basis.
AWS is not competing to be the cheap, low-margin host for YourFreeImageSite.Com and so their prices are going to be different on that point.
At a grocery store: 24 pack of Coke being $7 but one 20oz bottle being 1.99?
Or that $6 coke at the movies, ballpark, or Disneyland?
To fix it, let's change it from buy per bag to per gram you want to leave the store.
So your canned soup costs at least 3 times more to leave the supermarket then in cost to buy it than to eat it in the supermarket.
This is not even an exaggeration. s3 is 0.024/GB and egress bandwidth is 0.09/GB
Nobody is paying for egress, they are paying for everything else.
AWS is focused on corporate IT so egress was always a secondary thing for them.
It might actually be more profitable for them to have uber-markups on that egress then to serve the web space that requires cheap bandwidth.
As for your assertion that there's a price fixing conspiracy, who do you imagine they're colluding with? What other company do you find charging these prices?
AWS wasn't meant to support Netflix type loads, those guys will build their own CDN's. For everyone else who wants security groups (totally for free) when some other firewall vendors would charge a small fortune to provision 1Gbps capacity for these types of services... they are fine with the price.
The other issue cloudflare doesn't understand is the bandwidth pricing they quote is for capacity (ie, 10Gbps). AWS has to have enough capacity to serve the peak, but the customer only has to pay for data used. I'm sure at low points the data is free, but maintaining the black friday / superbowl capacity is expensive, so you are paying a premium for that too.
> Netflix uses Amazon Web Services (AWS) for nearly all its computing and storage needs, including databases, analytics, recommendation engines, video transcoding, and more—hundreds of functions that in total use more than 100,000 server instances on AWS.
https://aws.amazon.com/solutions/case-studies/netflix-kinesi...
It also has it's own entirely separate content delivery system, Open Connect. https://blog.apnic.net/2018/06/20/netflix-content-distributi...
>Netflix Open Connect is our purpose-built Content Delivery Network (CDN) responsible for serving 100% of our video traffic.
2) $50/TB may not be a big part of some customers bills. If it is on cloudfront you drop to 0.02/GB or $20/TB for larger volumes.
3) AWS doesn't charge separately for some services that wrap around networking. Their nitro instances have a pretty good networking story.
4) Especially with this new free tier on cloudfront, a fair number of users will never hit 1TB per month (free) data.
Nobody ever got fired for using AWS.
BTW you don't need to "run your own server" per se on the bare metal or VPS providers. You can auto-provision with Terraform, run Kubernetes or Nomad/Consul, etc. You have to do some work to set up your templates and the environment you will use but once it's created you can stamp out copies of it endlessly.
There are cases where AWS et. al. make sense. The bottom line is that you need to do your own spreadsheets modeling your own workload and compare costs. Include extra labor for managing your own stuff and compare it to the added costs of AWS.
What you'll often find is that AWS and such are cheaper at a small to medium scale and DIY becomes cheaper (sometimes radically so) at larger scale.
If you max out that connection non-stop, you can push about 330 TB/month. The same amount of bandwidth from EC2 would cost roughly US$20,000.
These companies are still pretty profitable.
If you colocate your own hardware you can go even lower than the bare metal hosts.
They also offer comparatively much cheaper hardware, which is why I've been using them for all my heavy workloads for 8+ years.
I have seen large scale deals where CloudFront comes in cheaper than what the smaller CDNs built on bare mantel can reasonably offer even with sizable commits.
VPS providers like Vultr and Digital Ocean are a bit more but still a lot cheaper than the big three.
Bandwidth prices at the big clouds are ludicrously high.
That's a pretty direct dig at cloudflare with their service and data type limitations :) So this does seem pretty cloudflare targeted.
I've come to the conclusion that Cloudflare's CDN is only really worthwhile if I'm building something tiny and basic that will never conceivably need any of their enterprise features (and I've turned out to be wrong about this down the line on many occasions, so YMMV), or something super ambitious where I'm willing and able to go all in on the enterprise plan and hope that eventually economies of scale on egress costs will kick in and turn it into a good deal. That leaves a giant gaping hole in the middle where it makes more sense to go with a different CDN like Cloudfront or Fastly where the bandwidth isn't free, but advanced features are included or charged on a usage basis (these days most of my projects fall into this category).
You think they would be lowering their cost if it wasn’t for R2 or whatever they call it? Of course not!
“Hey, look at Cloudflare, should we reduce egress costs?”
“Absolutely not, but let’s make a free tier change and hope that fewer people hassle us about that”
It’s a signal that they’re digging in on the price structure.
"Hey should we build our company on cloudflare? Their egress cost is cheaper"
"No, AWS has far more features and besides, we get enough bandwidth for free because we're a small startup"
Fast forward 5 years, your company has grown and is buying a 10 terabytes a month of egress, but you can't switch platforms now, you're too far dug in and integrated with AWS.
Let's be clear, you can build a functional startup on AWS free of charge assuming you at least have a valid credit card.
The .01% who eventually become enterprise clients aren't going to complain.
For high volume customers this isn't going to make a huge difference. For many who were considering Cloudflare, it could mean their service is now free.
So I guess... it depends how you look at it.
My guess is that the majority of their revenue is coming from a few big customers, for whom this is not a relevant discount at all. I thinkt that they are introducing this offer to get developers to adopt AWS for small projects, hoping that they'll then use the same service they are already familiar with for big projects.
A very significant percentage of their revenue comes from Netlix, Heroku, and several others that run their entire infrastructure on AWS.
AWS can't do too much to clients with the capital to build their own data systems
In other words, if 151 TB total is consumed:
* first 150 TB at full price
* next 1 TB discounted
This is about courting developers. If Cloudflare is going to make it free to play with all their tools, and only start charging when usage becomes "real" then they have a good chance of winning over the dev community. AWS can't let that happen, because they know then the enterprise rot will start.
> Free data transfer out of CloudFront is no longer limited to the first 12 months. [..,] Free data transfer out from AWS Regions is also no longer limited to the first 12 months.
Just hope you don't get over a TB, or it's going to be expensive quickly!
For big customers this is not going to make any difference at all.
What’s interesting is they view this as a way to increase profits instead becoming slightly more competitive by reducing what they charge per TB of bandwidth.
if you pay for outgoing bandwidth on AWS, your bill will go down. that's a price reduction.
$5 off a turkey wrap is still a price reduction. whether or not your were shopping for a lamborghini isn't really relevant.
What it does do, however, is favor their CDN over the competition. If you use Cloudflare, Fastly, Akamai, etc. you used to pay roughly the same egress rate as a CloudFront customer, but now you hit the free tier limit 10 times faster.
[1] https://aws.amazon.com/blogs/aws/aws-free-tier-data-transfer...
Sounds like SOMEBODY over there is trying to address the Bandwidth Alliance announcement.
Amazon’s AWS margin is everyone else’s opportunity.
Dude if you re sad you re paid a dollar too short in a warehouse, bullshitting about infra boycott will accomplish nothing, or at best, punish aws for something they cant control.
Build a competitor if it s so easy to do the warehousing ethically, and you might even end up having amazon contract you if you re brilliant and cheap.
[1] https://blog.cloudflare.com/introducing-r2-object-storage/
Even AWS's own Lightsail (which is so throttled that it's a far inferior solution to most of the other VPS/"cloud" providers) includes at least 1TB of transfer for free.
In our internal testing, it appears that AWS often applies the egress pricing twice, both when leaving the AZ where your instance(s) are located as well as again in the region where your customers are, after traveling through the AWS internal network; the first is an inter-AZ transfer, and the second is the actual egress from AWS' network.
So, it appears that the egress fees are nearly always not merely the oft-cited 8,000% greater than competitors, but twice that. AWS is not very transparent about this.
Understatement of the year: "Data transfer charges are often overlooked while architecting a solution in AWS."[0]
0. https://aws.amazon.com/blogs/architecture/overview-of-data-t...
As a new user, I was working on publishing open source documentation via CloudFront (https://tmuxp.git-pull.com) and made a mistake of invalidating '*', and doing it every time I pushed to CI. This was sphinx-doc, so no cache-busting filenames.
My bill was absolutely enormous. I chewed threw the free tier credits.
If CloudFront ever gets more generous with invalidations, that'd help reduce the sting for those of us that make those early mistakes.
[1] https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope...
For gatsby sites and webpack apps, I did ultimately figure out and simplify my s3 / cloudfront deploys and only invalidate index.html.
Ultimately it looks like I'm going to be migrating away to sphinx-doc. It's not up to date with the best practices in static site apps these days.
It’s introducing more free tier, but once you blow past that, the costs add up again.
I'm also trying to unpack "legitimize" to something more concrete... One possibility is that AWS's action is a signal of AWS customers' moving business to Cloudflare (that we wouldn't otherwise know about). Or perhaps it's simply AWS flinching and consequently customers perceive Cloudflare as more legitimate and move more business there?
AWS had growth of $1.2B in last quarter? I think AWS is still hitting something like 30%+ revenue growth YoY even though they are already huge?
With this size / scale, AWS should be able predate someone like cloudflare on base pricing.
I do think cloudflare may be able to evolve their products faster given they aren't carrying around x billion of recurring revenue.
Cloudflare simply doesn't share egress pricing.
1) They do not have public egress pricing. That should be a red flag at this time.
2) They are currently LOSING a lot of money on their offerings - AWS makes a ton. That should be red flag #2.
This is not interesting without more context. If they lose money because their income is below costs, that's a problem. If they lose money because they have headroom and spend all of it on customer acquisition, that's an opposite of a problem.
One thing - is their free service offering a sales and marketing expense or is that in cost of revenue.
Last quarter they did 80M in sales costs (vs 40 in R&D and 28 in G&A). Sales costs were 50% of operating costs and close to 50% of revenue.
Amazon has everything blended, but sales runs 7% of revenue.