Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is a risk any time you host anything on the internet on any system that charges you for storage, bandwidth or CPU usage. It's fine to take that risk on as long as you're aware of it and keep an eye on your spend.

In this case I'm nervous because 43GB is a lot larger than most projects!



I think the point is that not every host charges for bandwidth or CPU usage, making S3 particularly risky.


There's no CPU charge, only per-request charges.

Bandwidth is free into S3 or from S3 to another AWS service so it's particularly handy for that use case.


For S3, yes.




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

Search: