[flagged]
A $1k AWS mistake
31–40 of 281 posts
Re: A $1k AWS mistake
#32Why are people still using AWS?
And then writing “I regret it” posts that end up on HN.
Why are people not getting the message to not use AWS?
There’s SO MANY other faster cheaper less complex more reliable options but people continue to use AWS. It makes no sense.
Re: A $1k AWS mistake
#33> AWS charges $0.09 per GB for data transfer out to the internet from most regions, which adds up fast when you're moving terabytes of data. How does this actually work? So you upload your data to AWS S3 and then if you wish to get it back, you pay per GB of what you stored there?
Made in California.
We are programmed to receive. You can check out any time you like, but you can never leave
Re: A $1k AWS mistake
#34Earlier quoted context omitted.
Yes…? Egress bandwidth costs money. Consumer cloud services bake it into a monthly price, and if you’re downloading too much, they throttle you. You can’t download unlimited terabytes from Google Drive. You’ll get a message that reads something like: “Quota exceeded, try again later.” — which also sucks if you happen to need your data from Drive. AWS is not a consumer service so they make you think about the cost dir…
"Premium bandwidth" which AWS/Amazon markets to less understanding developers is almost a scam. By now, software developers think data centers, ISPs and others part of the peering on the internet pay per GB transferred, because all the clouds charge them like that.
Try a single threaded download from Hetzner Finland versus eu-north-1 to a remote (i.e. Australia) destination and you'll see premium bandwidth is very real. Google Cloud Storage significantly more so than AWS.
Sure you can just ram more connections through the lossy links from budget providers or use obscure protocols, but there's a real difference.
Whether it's fairly priced, I suspect not.
Re: A $1k AWS mistake
#35I made the same mistake and blew $60k. I have never understood why the S3 endpoint isn't deployed by default, except to catch people making this exact mistake.
[deleted]
Re: A $1k AWS mistake
#36Just curious but if you are already on Hetzner, why not do the processing also there?
Re: A $1k AWS mistake
#37These sort of things show up about once a day between the three big cloud subreddit. Often with larger amounts
And it’s always the same - clouds refuse to provide anything more than alerts (that are delayed) and your only option is prayer and begging for mercy.
Followed by people claiming with absolute certainty that it’s literally technically impossible to provide hard capped accounts to tinkerers despite there being accounts like that in existence already (some azure accounts are hardcapped by amount but ofc that’s not loudly advertised).
Re: A $1k AWS mistake
#38As a bootstrapped dev, reading stories like these gives me so much anxiety. I just can’t bring myself to use AWS even despite its advantages.
Re: A $1k AWS mistake
#39Why are people still using AWS? And then writing “I regret it” posts that end up on HN. Why are people not getting the message to not use AWS? There’s SO MANY other faster cheaper less complex more reliable options but people continue to use AWS. It makes no sense.
Examples?
Re: A $1k AWS mistake
#40Ah, the good old VPC NAT Gateway. I was lucky to have experienced all of the same mistakes for free (ex-Amazon employee). My manager just got an email saying the costs had gone through the roof and asked me to look into it. Feel bad for anyone that actually needs to cough up money for these dark patterns.
Personally I don't even understand why NAT gateways are so prevalent. What you want most of the time is just an Internet gateway.
Only works in public subnets, which isn't what you want most of the time.