Yeah you're likely having issues due to memory constraints. Most of the tutorial can be completed without Cloudera Manager in 4GB if RAM, if you want to start with a new instance of the VM. Other than checking the status of required services before each tutorial in the sequence, the only thing missing will be using Cloudera Navigator at the end (which will actually require 10GB+ of memory to launch the Cloudera Enterprise (trial) option) to audit access to the cluster, data lineage, and security policies. ... View more

The clock offset issue is likely due to networking configuration, and may not actually be serious. Cloudera Manager wants to make sure all the machines' clocks are in sync via NTP. If your VM can't reach the NTP servers CentOS 6 is configured with be default (often because VMware is set to a host-only virtual network adapter) it will trigger this warning. If after restarting the service monitor you're only seeing this warning and services marked as red because of the host they're running on (I.e. As a side effect of this warning) you can safely ignore the warning (if you don't need to dismiss anything from the internet, or tweak VMware's network setting to allow network access. ... View more

Paul, It is possible to repair the instance by mounting it's EBS volume on another instance and copying the key files from another working instance in the cluster (since they all accept the same key). You would need to do this manually, however - It's not something Cloudera Live can do. It has no direct access to your account. It works by SSH credentials set up by the instances, and then deletes these keys when it's finished. There are several blog and forum posts detailing how to do this, e.g. http://automagical.rationalmind.net/2015/09/28/regain-access-aws-ec2-instance-lost-access/. It is a tricky procedure. If you don't have valuable data on this cluster, you may also consider deleting your cluster, registering for a new access code and starting a new cluster. ... View more

It should cost a little less than $30 per day if you accept the default instance sizes when you're deploying. The year-long free tier on AWS probably doesn't apply because it limits you to a couple of very small instances. Once you submit the deployment it takes a bit less than an hour to be ready, and the tutorial may take you a couple of hours or less. If you want to save your progress but take a break (e.g. overnight), you can stop the instances and restart them, however they'll come back with different IP addresses, so you'll need to look up the new IP address to log into as the links in your email will have the original address. More details are in the docs: http://www.cloudera.com/content/www/en-us/get-started/cloudera-live/aws-documentation.html If cost is a concern, you may prefer the QuickStart VM. It includes an almost identical tutorial, but it runs on your workstation instead of the cloud. Hope that helps! ... View more

I believe calling it the 'Enterprise' VM is new wording and I agree it's confusing - I'll try get that changed. There is only that 1 VM. By default it will launch CDH and require 4GB of RAM. The options to launch Cloudera Manager (with either the Express our Enterprise (trial) license) are on the Desktop once you boot the VM. ... View more

Within a few minutes of the CloudFormation stack being deployed, it should get marked in a green state with "CREATE_COMPLETE" or a red state with "ROLLBACK_COMPLETE". If it's green, you should receive another email in a few minutes with a link to a progress bar, and your final email within about 45 minutes with credentials, etc. If the stack is marked in red, there was a problem and you'll need to look up the specific errors under the Events tab.   If your stack has been green but you have not received the next email within 15 - 20 minutes, send me a private message with your access code and I can look into what's going on with that cluster. ... View more

Also note that when you just run 'ls' or 'pwd', that's referring to your local / native filesystem. What directory you are currently in in your shell has no effect on what directory it shows you when you say 'hdfs dfs -ls'. Now, there's a /usr directory on the local / native filesystem, but that's a complete separate idea from the /user directory in HDFS. ... View more