Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A $1k AWS mistake

geocod.io

Post reply on HN
Print view View original

61–70 of 281 posts

Re: A $1k AWS mistake

#61

Post by andrewstuart »

wiether wrote: post #59
andrewstuart wrote: post #57

Earlier quoted context omitted.

Allow me to google that for you….. https://www.ionos.com/servers/cloud-vps $22/month for 18 months with a 3-year term 12 vCores CPU 24 GB RAM 720 GB NVMe Unlimited 1Gbps traffic

AWS is not just EC2 And even EC2 is not just a VPS If you need a simple VPS, yes, by all means, don't use AWS. For this usecase AWS is definitely not cheaper nor simpler. Nobody said that. Ever.

They’re Linux computers.

Anything AWS does you can run on Linux computers.

It’s naive to think that AWS is some sort of magically special system that transcends other networked computers, out of brand loyalty.

That’s the AWS kool aid that makes otherwise clever people think there’s no way any organization can run their own computer systems - only AWS has the skills for that.

Re: A $1k AWS mistake

#62

Post by wiether »

andrewstuart wrote: post #61
wiether wrote: post #59

Earlier quoted context omitted.

AWS is not just EC2 And even EC2 is not just a VPS If you need a simple VPS, yes, by all means, don't use AWS. For this usecase AWS is definitely not cheaper nor simpler. Nobody said that. Ever.

They’re Linux computers. Anything AWS does you can run on Linux computers. It’s naive to think that AWS is some sort of magically special system that transcends other networked computers, out of brand loyalty. That’s the AWS kool aid that makes otherwise clever people think there’s no way any organization can run their own computer systems - only AWS has the skills for that.

It was already clear that you were in bad faith here when you suggested a VPS to replace AWS, no need to insist.

But you are absolutely right, I'm drinking the AWS kool aid like thousands of other otherwise clever people who don't know that AWS is just Linux computers!

Re: A $1k AWS mistake

#63

Post by wiether »

viraptor wrote: post #60
wiether wrote: post #41

Earlier quoted context omitted.

Reading all the posts about people who got bitten by some policies on AWS, I think they should create two modes: - raw - click-ops Because, when you build your infra from scratch on AWS, you absolutely don't want the service gateways to exist by default. You want to have full control on everything, and that's how it works now. You don't want AWS to insert routes in your route tables on your behalf. Or worse, having h…

> you absolutely don't want the service gateways to exist by default. Why? My work life is in terraform and cloudformation and I can't think of a reason you wouldn't want to have those by default. I mean I can come up with some crazy excuses, but not any realistic scenario. Have you got any? (I'm assuming here that they'd make the performance impact ~0 for the vpc setup since everyone would depend on it)

Because I want my TF to reflect exactly my infra.

If I declare two aws_route resources for my route table, I don't want a third route existing and being invisible.

I agree that there is no logical reason to not want a service gateway, but it doesn't mean that it should be here by default.

The same way you need to provision an Internet Gateway, you should create your services gateways by yourself. TF modules are here to make it easier.

Everything that comes by default won't appear in your TF, so it becomes invisible and the only way to know that it exists is to remember that it's here by default.

Re: A $1k AWS mistake

#64

Post by sixtyj »

rikafurude21 wrote: post #27
dabiged wrote: post #13

I 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.

Thats a year salary but hey think about how much more complicated your work would be if you had to learn to self-host your infra!

Text je srozumitelný, ale angličtina je neuhlazená. Funkční verze:

Cloud cult was successfully promoted by all major players, and people have completely forgotten about the possibilities of traditional hosting.

But when I see a setup form for an AWS service or the never-ending list of AWS offerings, I get stuck almost immediately.

Re: A $1k AWS mistake

#65

Post by benmmurphy »

viraptor wrote: post #11

The service gateways are such a weird thing in AWS. There seems to be no reason not to use them and it's like they only exist as a trap for the unaware.

the gateway endpoints are free (s3 + dynamodb?), but the service endpoints are charged so that could be a reason why people don't use the service endpoints. but there doesn't seem to be a good reason for not using the service gateways. it also seems crazy that AWS charges you to connect to their own services without a public ip. also, i guess this would be less of an issue (in terms of requiring a public ip) if all of AWS services were available over ipv6. because then you would not need NAT gateways to connect to AWS services when you don't have a public ipv4 ip and I assume you are not getting these special traffic charges when connecting to the AWS services with a public ipv6 address.

Re: A $1k AWS mistake

#66

Post by ed_elliott_asc »

sofixa wrote: post #55
Havoc wrote: post #37

These 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 bein…

It's not that it's technically impossible. The very simple problem is that there is no way of providing hard spend caps without giving you the opportunity to bring down your whole production environment when the cap is met. No cloud provides wants to give their customers that much rope to hang themselves with. You just know too many customers will do it wrong or will forget to update the cap or will not coordinate in…

Let people take the risk - somethings in production are less important than others.

Re: A $1k AWS mistake

#67

Post by cenamus »

sixtyj wrote: post #64
rikafurude21 wrote: post #27

Earlier quoted context omitted.

Thats a year salary but hey think about how much more complicated your work would be if you had to learn to self-host your infra!

Text je srozumitelný, ale angličtina je neuhlazená. Funkční verze: Cloud cult was successfully promoted by all major players, and people have completely forgotten about the possibilities of traditional hosting. But when I see a setup form for an AWS service or the never-ending list of AWS offerings, I get stuck almost immediately.

Čech?

Re: A $1k AWS mistake

#69

Post by archerx »

sofixa wrote: post #55
Havoc wrote: post #37

These 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 bein…

It's not that it's technically impossible. The very simple problem is that there is no way of providing hard spend caps without giving you the opportunity to bring down your whole production environment when the cap is met. No cloud provides wants to give their customers that much rope to hang themselves with. You just know too many customers will do it wrong or will forget to update the cap or will not coordinate in…

Old hosts used to do that. 20 years ago when my podcast started getting popular I was hit with a bandwidth limit exceeded screen/warning. I was broke at the time and could not have afforded the overages (back then the cost per gig was crazy). The podcast not being downloadable for two days wasn’t the end of the world. Thankfully for me the limit was reached at the end of the month.

Re: A $1k AWS mistake

#70

Post by conception »

fergie wrote: post #68

Is it possible for hobbyists to set a hard cut off for spending? Like, "SHUT EVERYTHING DOWN IF COSTS EXCEED $50"

Yes, but you have to program it. And there is a little bit of whack so it might be $51 or something like that.
Post reply on HN