We setup a batch compute environment, job queue, and job definition. The min CPUs for the compute environment is set to 16, so it should always have at least one EC2 instance running. It's a MANAGED
environment. It is not starting any, yet everything is still reporting healthy. I've looked at the troubleshooting page and nothing useful has come of it yet.
Where can I go to see what is going wrong? Is this completely a black box and if I make a mistake somewhere in my config (Probable some kind of ARN permissions problem), I have to scan every line till I happen to see the mistake?
The answer is, look at EC2 Auto Scaling Groups. There should be an autoscaling group named after the compute environment. All of the errors for starting EC2 instances should be in that auto scaling group, which is created and managed by the batch compute environment.