> There should be a better way to figure out what my execution environment looks like than trial and error. To be fair, once you start to be bothered with how

> There should be a better way to figure out what my execution environment looks like than trial and error. To be fair, once you start to be bothered with how many threads you get, I'd argue you are already way outside of AWS Lambda's domain and well inside plain old ECW/ECS territory. Keep in mind that AWS Lambdas are appropriate for a) glue code to plug together AWS events b) offload seldomly-ran background tasks, c) rarely executed tasks, such as a terribly simple REST API that is simpler to develop and maintain as a API Gateway+Lambda app instead of, say, express/spring/flask/whatever. Once your requirements don't unquestionably fit any of these scenarios, you have to take a very hard look at what you're doing to explain why aren't you just rolling your own web service and instead you're opting to both pay a premium and increase your maintenance needs.