21–30 of 168 posts
9 cents a gigabyte downloaded versus 0 cents a gigabyte downloaded is a pretty good deal. There’s not much AWS can do about it because they must make untold billions from those sweet, sweet S3 egress fees. I’d be willing to bet S3 egress fees make up about 60% of all AWS revenue.
Our last month invoice was only $0.26 for 26GB+ of managed storage.
9 cents a gigabyte downloaded versus 0 cents a gigabyte downloaded is a pretty good deal. There’s not much AWS can do about it because they must make untold billions from those sweet, sweet S3 egress fees. I’d be willing to bet S3 egress fees make up about 60% of all AWS revenue.
I have to imagine CloudWatch makes AWS a lot of money too. Very often, when I look into an account from work that is spending a lot, CloudWatch is a large contributor.
9 cents a gigabyte downloaded versus 0 cents a gigabyte downloaded is a pretty good deal. There’s not much AWS can do about it because they must make untold billions from those sweet, sweet S3 egress fees. I’d be willing to bet S3 egress fees make up about 60% of all AWS revenue.
Eg. For cloudflare workers. If you're worker is making an outgoing request ( db / rest) it's not considered cpu-time and it's not counted towards that either ( in cloudflare ofc).
While this is a hidden profit of many cloud providers :)
vampire attack, nice
Original source: https://blog.cloudflare.com/sippy-incremental-migration-s3-r...
Yeah the linked post is a bad rehash of the original blog post. Thanks for linking it.
This one shows you how to set it up in cloudflare.
While the info provided in both is indeed similar.
9 cents a gigabyte downloaded versus 0 cents a gigabyte downloaded is a pretty good deal. There’s not much AWS can do about it because they must make untold billions from those sweet, sweet S3 egress fees. I’d be willing to bet S3 egress fees make up about 60% of all AWS revenue.
That's not the only thing that has excess fees in AWS/Azure/ .... Eg. For cloudflare workers. If you're worker is making an outgoing request ( db / rest) it's not considered cpu-time and it's not counted towards that either ( in cloudflare ofc). While this is a hidden profit of many cloud providers :)
Wait time isn’t calculated as compute?
Earlier quoted context omitted.
This, CF is the only service that I find amazing, and that I do not use for anything. Compared to AWS, I think I prefer the "we're your unopinionated infra provider, if you want a WAF we have that too", vs the CF "block the world, especially the developing world, give zero craps about it". I fundamentally would be unhappy as their customer even if their service were stellar because I do not want my apps to be associa…
The problem is; as a tiny SaaS owner, we still get massive DDOS attacks a few times per year. With other services I would pay a fortune; with CF it’s free. Downtime has people walk away and CF saved my bacon many times. If there are friendlier alternatives that work as effective then I have not found. Mind you, I don’t mind paying a few 100$/mo for such a service but on aws etc one attack burns that for more than a y…
Wow, why? Extortion? Competition? Collateral damage?
Earlier quoted context omitted.
That's not the only thing that has excess fees in AWS/Azure/ .... Eg. For cloudflare workers. If you're worker is making an outgoing request ( db / rest) it's not considered cpu-time and it's not counted towards that either ( in cloudflare ofc). While this is a hidden profit of many cloud providers :)
Can you explain more? Wait time isn’t calculated as compute?
https://community.cloudflare.com/t/how-is-cpu-time-per-reque...
Cloudflare is only billing that actual cpu-time.
Edit: this is a better resource https://blog.cloudflare.com/workers-pricing-scale-to-zero/