The start.sh script was used to start the services, the stop.sh to stop them

The SAM solution was installed 4x on 4 EC instances, each one received the same error and clusters could not be created.

There is an isc_prometheus.yml file in the directory which by the default installation did not have 764 permissions.  I set the permissions to 764 and restarted the services and the same error is received.  Documentation is a bit light but I followed the instructions.  Has this worked for others as documented?

Any thoughts?  I'm pretty sure that it is not up to spec, although some parsers will be fine.  To be clear there needs to be a newline following each key value pairing per the Prometheus spec. 

Absolutely, as I am seeing more Cache' and IRIS instances pop up in customers, I'm excited to explore this more.  Feel free to reach out I'm happy to test or be a guinea pig on anything.  More than happy to help or collaborate anyway I can :). BTW, I'm seeing lots of community solutions for Cache' / Prometheus but it seems the SAM docs only refer to IRIS, is it not planned for Cache'?

I will pull down the latest version of SAM when available and retest this, I'll take steps to document each step.  It's entirely possible I'm making a mistake in my deployments that is causing consistent failures, if so I imagine that would be helpful to know.