Live data from Hacker News

Serverless Horrors

serverlesshorrors.com

11–20 of 503 posts

Re: Serverless Horrors

#11

I thought this would be about the horrors of hosting/developing/debugging on “Serverless” but it’s about pricing over-runs. I scrolled aimlessly through the site ignoring most posts (bandwidth usage bills aren’t super interesting) but I did see this one: https://medium.com/@maciej.pocwierz/how-an-empty-s3-bucket-c... About how you make unauth’d API calls to an s3 bucket you don’t own to run up the costs. That was a n…

[deleted]

Re: Serverless Horrors

#12
post #10

> I had cloudflare in front of my stuff. Hacker found an uncached object and hit it 100M+ times. I stopped that and then they found my origin bucket and hit that directly. Pardon my ignorance, but isn’t that something that can happen to anyone? Uncached objects are not something as serious as leaving port 22 open with a weak password (or is it?). Also, aren’t S3 resources (like images) public so that anyone can hit t…

No, s3 objects should always be private and then have a cloudfront proxy in front of them at the least. You should always have people hitting a cache for things like images.

Re: Serverless Horrors

#13
post #2

After a quick check on Vercel stories, it seems all payments were discarded or mistakes in the first place. Does it really happen to really have to pay such a bill? Do you need to tweet about it to be reimbursed?

[deleted]

Re: Serverless Horrors

#14
post #10

> I had cloudflare in front of my stuff. Hacker found an uncached object and hit it 100M+ times. I stopped that and then they found my origin bucket and hit that directly. Pardon my ignorance, but isn’t that something that can happen to anyone? Uncached objects are not something as serious as leaving port 22 open with a weak password (or is it?). Also, aren’t S3 resources (like images) public so that anyone can hit t…

No. Your buckets should be private, with a security rule that they can only be accessed by your CDN provider, precisely to force the CDN to be used.

Re: Serverless Horrors

#16

I thought this would be about the horrors of hosting/developing/debugging on “Serverless” but it’s about pricing over-runs. I scrolled aimlessly through the site ignoring most posts (bandwidth usage bills aren’t super interesting) but I did see this one: https://medium.com/@maciej.pocwierz/how-an-empty-s3-bucket-c... About how you make unauth’d API calls to an s3 bucket you don’t own to run up the costs. That was a n…

> I thought this would be about the horrors of hosting/developing/debugging on “Serverless” but it’s about pricing over-runs.

Agreed about that. I was hired onto a team that inherited a large AWS Lambda backend and the opacity of the underlying platform (which is the value proposition of serverless!) has made it very painful when the going gets tough and you find bugs in your system down close to that layer (in our case, intermittent socket hangups trying to connect to the secrets extension). And since your local testing rig looks almost nothing like the deployed environment...

I have some toy stuff at home running on Google Cloud Functions and it works fine (and scale-to-zero is pretty handy for hiding in the free tier). But I struggle to imagine a scenario in a professional setting where I wouldn't prefer to just put an HTTP server/queue consumer in a container on ECS.

Re: Serverless Horrors

#17
Maintaining your own containers or VMs is hard considering how much risk appetite you have for the issues at infra level. So, yeah, when you complain about the costs of serverless, you are just paying for your low risk appetite low cost of your IT management.

Re: Serverless Horrors

#18
post #8
post #2

After a quick check on Vercel stories, it seems all payments were discarded or mistakes in the first place. Does it really happen to really have to pay such a bill? Do you need to tweet about it to be reimbursed?

No, at least in enterprise consulting for these kind of hosting, usually there is a contact person on the support team that one can reach directly. However these projects are measured in ways that make Oracle licenses rounding errors. Which naturally creates market segmentation on who gets tier 1 treatment and everyone else.

Once you're in a contract + TAM territory, pricing works very differently. Also, temporary experiments and usage overruns become an interesting experience where the company may just forget to bill you a few thousands $ just because nobody looked at the setup recently. Very different situation to a retail user getting unexpected extra usage.

Re: Serverless Horrors

#19
post #2

After a quick check on Vercel stories, it seems all payments were discarded or mistakes in the first place. Does it really happen to really have to pay such a bill? Do you need to tweet about it to be reimbursed?

Relying on the mercy of a support agent that may be having a bad day is a poor strategy

Re: Serverless Horrors

#20
post #10

> I had cloudflare in front of my stuff. Hacker found an uncached object and hit it 100M+ times. I stopped that and then they found my origin bucket and hit that directly. Pardon my ignorance, but isn’t that something that can happen to anyone? Uncached objects are not something as serious as leaving port 22 open with a weak password (or is it?). Also, aren’t S3 resources (like images) public so that anyone can hit t…

This story is giving "I leave OWASP top 10 vulns in my code because hacker mindset".

It's not that hard to configure access controls, they're probably cutting corners on other areas as well. I wouldn't trust anything this person is responsible for.

Post reply on HN