Uwe,
Bashing away at this with a hammer, being stubborn,, I thought I would spin up an m2.4xlarge instance of my troublesome AMI:
Despite being a little sluggish, the administration overview appeared after a couple of seconds (it hung on m2.2xlarge), here's the screenshot:
So, considering my two AMIs I have at the moment in relation to m2.2xlarge sizing.
- Upon fresh instance launch what is appearing to be consuming system resource to such effect that catalog/content and administration console requests hang, for one of the AMIs but not the other? And.....
- where the troublesome AMI fails with m2.2xlarge, it (just about) functions with m2.4xlarge, with administration console/catalog and content drilldown/SQL console select from public.schemas works (slowly).
I hope this additional information helps.