Intro to Node on AWS Lambda for S3 and Kinesis

Is there a way to automatically kill Lambda if the cost is going out of control because of an infinite loop? As a solo dev I cant be willing to bet hundreds or thousands of dollars potentially lost because of a bad piece of code I wrote. If thats possible it seems like a nice service that will save a lot of time not having to worry about doing server administration.<p>My ask HN post from earlier today basically asking the same thing <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9520964" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9520964</a>

I wish Lambda could listen to arbitrary TCP ports and respond e.g. to HTTP requests or MQTT messages. In the current form it seems pretty limited for any scenarios where generic clients initiate the requests, such as collecting device data and metrics. As I understand, currently the clients have to speak AWS-specific protocols to submit events &#x2F; data.

I really wish AWS would open up Lambda to more events than just S3 uploads and SQS &#x2F; Dynamo queues. There are so many workloads I could move to Lambda if I could just invoke it via an API call.