For what it's worth, there is a complementary (early stage) project a colleague of mine is working on where the idea is to let you leverage cloud formation from the command line and get closer to what you're talking about (deployment of a more complex infrastructure rather than just a single instance):
This looks nice. I'm currently in the process of creating a deployment script to cluster out wowza media server with a edge/origin setup ,auto scaling and loadbalancer setup. Really wish beanstalk was less error prone and worked 100% of the time.BTW does anyone know if beanstalk supports paid Ami's ?
Our problem is the the number of simultaneous connections we can support isn't static, it varies depending on the type of traffic bursts (i.e. New vs. Returning users).
But agree that a higher level proxy is useful - because this way your overloaded application doesn't even need to deal with traffic (we hope to use toobusy to have applications instruct the routing layer to temporarily block / reroute traffic in times of load).
The reason that I asked that is I feel that most applications end up needing something at that layer eventually anyways, but not knowing exactly what level of traffic results in too much load is a good reason to do this.
Actually I went to the Documentation and clicked the link there, which actually takes you to the github source. Completely my bad, having a license header is not abnormal. I jumped the gun because the Open Web Apps shim wasn't minified for quite a while.
If the former, it's in my opinion a question of what you're looking for. Here's my best response: https://hacks.mozilla.org/2013/05/introducing-awsbox-the-diy...