t2.micro is definitely too small to run all the services. You will immediately get memory exceptions and the JVMs will fail to start for various services (not only Cloudera Manager). t2.micro is also too small to run Director itself.    For a small development type of setup I would recommend m1.medium or larger (it depends on how much data you want to process with the cluster).   If your goal is to use Hue and experiment with various products have you considered Cloudera Live? ... View more

That's great! Any improvement ideas for future release? How could we improve the overall experience of using the product?  ... View more

Hi Natty! Have you been able to successfully run Director? Any feedback for future releases?     ... View more

That's great! Can you add a few more details on how you are planning to use Director? It would be useful to make sure future release are aligned with your requirements.  ... View more

With regard to "First Run" failure - there should another log message above that explains why that command actually failed and during what step. In the Cloudera Manager UI you should be able to see more details in the command history.  ... View more

There is something concerning in the output:   * Invalid role type(s) specified. Ignored during role creation: HUE: BEESWAX_SERVER ... done    Can you please remove BEESWAX_SERVER from the list of roles and retry? ... View more

First of all thanks for using Cloudera Director! I am happy to see everything worked fine while configuring multiple medium size clusters.    With regard to m2.4xlarge - there is no reason why it shouldn't work when running a supported operating system. I'm re-testing this now. Actually Director should work just fine with any instance type provided by AWS (using either SSDs or magnetic drives for ephemeral storage).    In terms of operating systems Director currently works with Red Hat Enterprise Linux 6.4 (PV or HVM)) or CentOS 6.4 (the official AMI from the AWS Marketplace). Amazon Linux (ami-f032acc0) is not currently supported.      ... View more

Hi David -    Have you changed the default Cloudera Manager password from admin/admin to somethind else? That may be the source of this error.  ... View more

There may be a mistmatch between the region you want to use and the one that has your key. Most of the resources in AWS are scoped to regions and can't be referenced globally.    The ".pem" extension is not needed.  ... View more