Hacker News new | past | comments | ask | show | jobs | submit login

AWS S3 scares the shit out of me.

The company I worked for misconfiguration one of the buckets and allowed uploads. A couple of months later there was a bill for $15k. Since apparently some spammers were using our service. Which is OK for a company but I would not want to use it as a private individual.






I have never had to use them directly but the use-now-pay-later model feels scary to me for the same reason. Maybe they allow setting the upper cap to the monthly bill (crossing which they don't serve you until you intervene) but I have never heard of it. On the other hand there are many stories extremely ballooned bills for some unforeseen reasons.

They have "AWS Budgets" for alerting you if you go over an amount but no automatic stops.

Notwithstanding the fact that this was a user misconfiguration, S3 allows you to configure public access blocks to prevent this sort of thing.

These days, you have to remove the public access block AND explicitly write a bucket policy (or set up deprecated ACLs) to allow public access.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: