Broken with 7.1 about quickstart-splunk-enterprise HOT 5 CLOSED

From further investigation I have suspicion that this bug is mostly related to changes in the AMI.

I am using ami-9808acfa (ap-southeast-2) which has a Splunk guid set by default which gets in the way when trying to build clusters (nodes can't join clusters when the master has the same guid). Its also has an AWS style local IP server name set which gets confusing.

I have created a fork with a fix, its not PR worthy but it works:
https://github.com/mikegchambers/quickstart-splunk-enterprise

from quickstart-splunk-enterprise.

@mikegchambers Thanks for reporting the issue. I'll take a look into it and get back to you.

from quickstart-splunk-enterprise.

also can't access splunk web with config password. So I roll back to March 2018's template and it works.

But in splunk web login page, it shows license expired. Is it because 60 day trial license is based on commit time of this script? i.e. if I use 2018 March version, it will expired at June?

Anyone can help me? Thanks a lot :)

from quickstart-splunk-enterprise.

@AndyHuang1991 the first fix I outlined in my OP enables you to login with the password you set. If you know your way around Splunk there are other things you will need to fix from there on.

FWIW: I had no issues with licenses uploaded via S3.

The problem with the March 2018 template (as you probably know) is that it references v7.0.0.

from quickstart-splunk-enterprise.

@mikegchambers @AndyHuang1991 These issues have been fixed.

from quickstart-splunk-enterprise.