Serverless Horrors

Post by 63stack » Mon, Sep 08, 2025, 10:13 PM UTC

belter wrote: post #360

phoenixhaber wrote: post #43

When I was learning to program through a bootcamp I spun up an elastic beanstalk instance that was free but required a credit card to prove your identity. No problem that makes sense - it's an easy way to prove authentication as a bot can't spam a credit card (or else it would be financial fraud and most likely a felony). Amazon then charged me one hundred thousand dollars as the server was hit by bot spam. I had the…

Did you do any training before launching the elastic beanstalk instance, or you just though a F-16 should be pretty easy to fly, at least according to most pilots?

Post by 63stack » Mon, Sep 08, 2025, 10:18 PM UTC

small_scombrus wrote: post #449

franktankbank wrote: post #26

Earlier quoted context omitted.

Seems an interesting oversight. I can just imagine the roundtable, uhh guys who do we charge for 403? Who can we charge? But what if people hit random buckets as an attack? Great!

> I can just imagine the roundtable That's the best part! The devs probably never thought of it, the support people who were complained to were probably either unable to reach the devs, or time crunched enough to not be able to, and who as a project manager would want to say they told their Devs to fix an issue that will lose the company money!

Post by JustExAWS » Tue, Sep 09, 2025, 12:04 AM UTC

x0x0 wrote: post #417

JustExAWS wrote: post #277

Earlier quoted context omitted.

I have had a “larger account” when I was at startup and was able to ask for a refund for a business. As I asked before, if what is causing overages is not web requests but storage should they just delete everything?

You, but shorter: It can't be done perfectly in 100.0% of all possible circumstances, so better to do absolutely nothing at all. On an unrelated note, this strongly aligns with their economic interests. For storage specifically, in that circumstance, if you weren't hellbent on claiming otherwise: it's easy to figure out what to do. For storage: block writes and reach out to the customer. Also, people are extremely un…

Post by bingabingabinga » Tue, Sep 09, 2025, 12:27 AM UTC

motorest wrote: post #159

bingabingabinga wrote: post #130

Earlier quoted context omitted.

I didn't use them, some bots did. Sort it out with them.

> I didn't use them, some bots did. Sort it out with them. For you to put together this sort of argument with a straight face, you need to have little to no understanding of how the internet in general, services and web apps work. Good luck arguing your case with a judge.

Post by raw_anon_1111 » Tue, Sep 09, 2025, 2:51 AM UTC

naasking wrote: post #488

raw_anon_1111 wrote: post #478

Earlier quoted context omitted.

Because your specific work case of how you want to disable processes is completely based on your requirements. AWS just gives you the tools.

I think "free or low cost tier that doesn't rack up a $100,000 bill" would be pretty common actually, enough to warrant a prominent preset template/option in their UI. They'd probably save a lot in support requests too.