Nagios Support Forum

Hello,

My company is currently using our own ELK stack and exploring Nagios Log Server for some of its built-in clustering and alerting capabilities.

I followed the instructions in the PDF below for creating an AWS instance with the log server pre-built, but I am unable to SSH and also the web admin does not seem to be running so I am stuck.
http://assets.nagios.com/downloads/nagi ... -Cloud.pdf

The document specifies I should be using the ec2-user user for SSH along with the key used to create the instance in EC2, but this is not working. I am getting "Permission denied (publickey,gssapi-keyex,gssapi-with-mic)." I double-checked that I am using the key that the Amazon EC2 console says is associated with the instance. I'm just using basic SSH:
I've verified I can ping the host and the command below seems to indicate port 22 is accessible: Ideas? I'm thinking I will just scrap these instances and install from the manual setup instructions, but that is a bit annoying.

Thanks

OK, I eventually figured this out.

I went down the path of installing manually, and as part of doing that I realized some environment problems that prevented the script on the pre-built image from running.

Specifically, these instances are running in a private subnet using a NAT instance for communicating with the outside world. The AWS security group wasn't allowing HTTP or NTP (UDP 123) through, issues I had to fix when doing the manual setup. The script on the image must just download the latest bits from Nagios and since it was unable to do that it must have just bailed and didn't even set up the SSH user appropriately.

It's a little annoying that you are completely locked out of the instance in a situation like this, but oh well. All set now.

Jon

Jon, I am glad your issue has been resolved! I am locking this topic. If you have any more questions/issues, please start a new thread.