EMR cluster gets terminated with error

Hello,

Thank you for raising your question in re:Post.

Based on what I can gather from your question, your attempts to create EMR Cluster fails with an error with no clear message on why or what the root cause is.

Cluster creation constitutes multiple steps, starting from requesting EC2 instances, installing the required services that coordinates the nodes in the cluster, installing bootstrap if you had any and at the very end installing the application you had selected.

Since there are no indicator from your question at what step this is failing, I would suggest you raise a case with AWS Support and our support engineers can take a look at your cluster and advise you on what would help.

While creation of the cluster you would have selected S3 path for cluster logs, if you did, do you see any logs in those directory? If not that would mean it is failing much earlier stage and could be related to the configuration you had selected eg: Custom AMI

If you do have logs in that location, have a look at the log files puppet.log.gz or stderr.log.gz in the location s3://<full-path-to-cluster-logs>/node/<Primary node instanceId>/provision-node/apps-phase/0/*/. If you have not worked with puppet logs before it may not be straightforward to find the error there and hence I would recommend you raise a case with us.

Hope this helps.

Hello,

Thank you for replying. Basic plan does not include premium support so you will not be able to raise a case with AWS Support. re:Post is public and hence we cannot discuss anything specific to a customers account here.

From the steps alone it is not clear what could cause the issue. Please navigate to the EMR console and locate the failed EMR cluster and click on it to look into the details. Once you are in Cluster details page do you see any additional error message when you click on the "Terminated with errors" status message? If yes, that should give us a hint of possible causes but please understand that it alone may not be enough to get to the root cause of the issue you are facing.

Also, do you see logs in the S3 path you configured for Cluster logs?