[untitled]
7 comments
(2024)
Previously: https://news.ycombinator.com/item?id=40203126
Previously: https://news.ycombinator.com/item?id=40203126
One of the items off the Serverless Horrors submission from today.
https://serverlesshorrors.com/all/aws-13k/ https://news.ycombinator.com/item?id=45157110
As noted in comments, AWS no longer charges for bad/unarhorized requests. https://aws.amazon.com/about-aws/whats-new/2024/08/amazon-s3...
The Serverless Horrors submission has some pretty amazing scenarios in it. Truly scary surprises!
https://serverlesshorrors.com/all/aws-13k/ https://news.ycombinator.com/item?id=45157110
As noted in comments, AWS no longer charges for bad/unarhorized requests. https://aws.amazon.com/about-aws/whats-new/2024/08/amazon-s3...
The Serverless Horrors submission has some pretty amazing scenarios in it. Truly scary surprises!
I always recommend using random strings for bucket names. If you want/need it to be human readable then use a random suffix instead.
It's been a year. Has it been disclosed what tool had this misconfiguration?
It's simple - stop using AWS ... or Azure ... or ... Follow DHH and learn to manage your own boxes.
TLDR: any kind of usage based billing, where you don't control the usage, will have issues of cost explosions. It doesn't matter much what it is exactly.
Get your own machines. Get colo instead of cloud.
Get your own machines. Get colo instead of cloud.
https://aws.amazon.com/about-aws/whats-new/2024/08/amazon-s3...