Deployment fails during SplunkCM EC2 Instance Creation

[auzroz]

I have attempted to remove the UserData from the SplunkCM resource, but the deployment then times out. Still troubleshooting this one.

[auzroz]

Looks like it is related to the following line in the UserData, this is present in all Instances. Based on running the exact command on the AMI manually, it throws an error where the sed command strips the variable out.
sed -i 's/ENFORCE_PWD_CHANGE=1//' /etc/init.d/splunk\n
This appears to alleviate the issue:
sed -i 's/ENFORCE_PWD_CHANGE=1/ENFORCE_PWD_CHANGE=0/' /etc/init.d/splunk\n

[tweaksalot]

will this completely resolve the issue? Is anyone else getting this as well? cc @sshvans
Can't seem to pass this error after 5 attempts. I'm blocked by this.

"CREATE_FAILED AWS::EC2::Instance SplunkCM Failed to receive 1 resource signal(s) within the specified duration
CREATE_IN_PROGRESS AWS::EC2::Instance SplunkCM Resource creation Initiated"

[auzroz]

I was able to finish the Quick Start guide by changing this, yes.

[spitzzz]

Having the same issue.

[billbartlett]

What options are you using when you experience this error? I just launched an unedited quickstart template in us-west-1 without any issue. My options of note were:

2 AZ
c4.2xlarge indexer instance type, 3 indexers
no pre-installed apps

Any additional information would be great so that I can replicate the issues seen in this thread.

[billbartlett]

This should be fixed now with PR#38

[augwyl]

I am still experiencing the same issue: CREATE_FAILED AWS::EC2::Instance SplunkCM Failed

I just launched an unedited quickstart template in ap-southeast-2 region. My options of note were:

3 AZ
c4.2xlarge indexer instance type, 3 indexers
no pre-installed apps

still failed