Amazon has avoided allowing users to set hard billing cap and that makes me worried a lot too. If your website gets suddenly too popular or DDoSed then you can

Amazon has avoided allowing users to set hard billing cap and that makes me worried a lot too. If your website gets suddenly too popular or DDoSed then you can get toast and might even go bankrupt. Amazon has reasoned that they don't want to disrupt your service by enabling this feature (because technically their safest choice to implement hard cap is to shutdown all resources assigned to you until you intervine). But as a user that's exactly what I want! I rather have my service go down then me go bankrupt from my ad-free website. It should be customer's choice to enable this feature if they want to but Amazon doesn't want to do it regardless of their supposedly "sharp" focus on customer needs. The feature they did enabled is CloudWatch where you get alerts if you go over the limit. But that's rather weak. If it happened while I was sleeping or on vacation, it is very easy to miss these notifications and face giant financial losses in just few hours. Having a non-commercial service hosted on AWS is like a sword hanging over your head that can fall anytime on you.