I&#x27;m playing with these exact things now and it is very enjoyable so far.<p>My main worry is not on the technical side but on how things are charged for. If I build something that starts to get used I am covered in terms of scalability, but not in a way that protects me from &#x27;cost scalability&#x27; so to speak. I know I can set up billing alerts and hit a big &#x27;shutdown&#x27; button in response to high load, but what I don&#x27;t think I can do is throttle these services based on the money I want to budget&#x2F;spend. With my own services I have a hard cost limit, with a hard scalability limit, or rather I just accept that my response times will go down or fail once I&#x27;ve allocated all I can afford.<p>If there something for AWS in terms of &#x27;cost throttling&#x27;? It may be a gap in their services, especially for people want to build things that might get traction?