Please check file permissions (the cloudera-director user should have write permissions) and restart the server.  ... View more

The underlying cause of the failure seems to be a failure to start Kafla:   [2016-02-01 19:10:58] ERROR [pipeline-thread-35] - c.c.l.b.UnboundedWaitForApiCommand: Command Start with ID 72 failed. Details: ApiCommand{id=72, name=Start, startTime=Mon Feb 01 19:10:10 EST 2016, endTime=Mon Feb 01 19:10:10 EST 2016, active=false, success=false, resultMessage=Failed to start service., serviceRef=ApiServiceRef{peerName=null, clusterName=Atlas-Test, serviceName=CD-KAFKA-MnViYSKk}, roleRef=null, hostRef=null, parent=null}   Cloudera Manager command execution history should have more details.    I believe get this error because the Kafka parcel is not distributed (as you know Kafka is not included in the CDH parcel). Please add "KAFKA: 0.8.2" to the products {} block. You may also need to add reference to the precise parcel repositories you want to use.      ... View more

It's likely that this is a transient error due to a network connectivity issue. Can you please retry? Do you get this failure in a consistent way?  ... View more

You can use rootVolumeSizeGB to expand a custom AMI.    The size of DFS can be managed indirectly by your choice of instance types. We have no other ways to control the number of ephemeral drives and we don't support EBS for data disks (only as the root partition).  ... View more

On eu-west-1 (Ireland) you could try the official CentOS 6.5 marketplace AMI with ID: ami-42718735  https://aws.amazon.com/marketplace/pp/B00IOYDTV6 (you can find it by clicking on Continue and on the Manual Launch tab)   Another option is to use RHEL 6.6 HVM community AMI with ID: ami-cf3b47b8  I found that by doing a search on the Community AMIs page for "rhel-6.6 hvm 2015".    It's good that you are using AmazonProvidedDNS because that's easiest option to start with.  ... View more