We have been using "Amazon Web Services". They should market their services more, they definitely have a bright future...
(I'm being tongue-in-cheek cheeky here.)
I know you're mostly pushing boundaries with your $150k figure, although at this point it wouldn't surprise me, but AWS is a professional tool aimed at professional engineers. They created Lightsail for "personal stuff."
Right tool for the right job, I guess? Although tyou can actually combine the two on a network level (Lightsail and AWS, that is.)
He's talking about the pricing model not the way to operate it. AWS bills for egress data. You can't operate it in any different way to stop that.
[a] which is fine if you're happy with the inflexibility that free Cloudflare offers. And you live in a country where the free tier doesn't have horrible routing (eg use the Sydney AWS region, put Cloudflare in front of it and then watch your traffic to/from Sydney take a round trip via the US or Singapore)
[b] every single AWS service charges egress fees (ie Cloudfront doesn't help at all)
[c] this does nothing for non-static assets
Am I missing something?
No, but you're not the OP above my comment, so my question still stands.
> (eg use the Sydney AWS region, put Cloudflare in front of it and then watch your traffic to/from Sydney take a round trip via the US or Singapore)
I don't understand? I don't have this issue (I'm in Brisbane; I use ap-southeast-2)
> [c] this does nothing for non-static assets
Non-static assets are going to be very tiny in most cases, and the problem then becomes about volume. If you've got volume and your business model doesn't suck, then you can afford the rate (my understanding is AWS' network egress charges are gross compared to other vendors.)
Every service on AWS charges egress fees that's my comment. There are other cloud operators that do not. I can safely run some static compute / storage / network at a fixed cost, you can't do this on AWS.
If too many people come to my website it won't wipe out my credit card. The site might go offline but I'd rather take that than a huge bill.
No provider on the planet gives you truly unlimited, fixed cost networking throughput. None.
AWS provides Lightsail for a fixed cost, static compute, storage, and networking solution. It's a not strawman argument just because you don't understand it.
There was no misconfiguration, just millions of DNS requests but not millions of actual users. I was in contact with AWS support multiple times. The only solution was so use AWS Shield Advanced. They did refund most of the charges but it was too risky for me. Even after I moved DNS provider there was DNS requests to the R53 zones. I can highly recommend https://dnsimple.com though.
I'm guessing AWS refunded close to 100% of fees associated with provable bad DNS requests.
AWS did do a refund but it requires me to monitor usage and do some investigation. I really don't want to spend time monitoring DNS requests.
But more important than that is of course to have a CloudFront cache infront of anything that exposes S3 storage.
Whereas, Lambda / Lambda@Edge / CloudFront Functions are of course wayyyyy more expensive (even if more capable) than workers.dev.
AWS doesn't push EB much, partly because it does offer great value and doesn't make them nearly as much money as things like FarGate or AppSync. If you need something that just does what really needs doing cheaply and well, though, give it another look.