The pain point for what you want there is the versioning and deployment side of things: how you update the application as atomically as possible.<p>I need to get Lambda Complex into real apps for a while in order to understand what is really, actually needed around the transition of the interface with other AWS resources on update of version. Currently I&#x27;m sure it&#x27;s going to be a major pain to have to write some code to redirect the flow of events to a different queue, but that&#x27;s still better in my mind than to try to manage versioning with a single queue or other source of events that is not included in the CloudFormation template or has to be managed as a special case during updates.<p>The other pain point is monitoring of the application state and clearing up after it. Lambda functions spawn infinite log groups in CloudWatch, and they don&#x27;t get deleted without some sort of automation to go do that. It isn&#x27;t clear to me what the best approach is at this point in time to attach monitoring and alerting to CloudWatch Logs. I&#x27;d almost rather leave them alone and primarily monitor via SQS queue attributes, leaving the CloudWatch logs for manual inspection.