Nagios Support Forum

I have created a new Virtual instance on AWS, but can not access through ssh Error message server refused connection
To verify the Access-Key, created anew instance and and able to ssh without any issue.

Console log for both instances are as under...

Amazon AMI did created the ssh-rsa finger prints, but Nagios AMI did not create any ssh-rsa finger prints. Its installation fail.


Amzon AMI : Console Log, it created fingerprint for rsa/ssh[/b]
Cloud-init v. 0.7.2 finished at Wed, 19 Nov 2014 19:11:42 +0000. Datasource DataSourceEc2. Up 85.91 seconds
ci-info: +Authorized keys from /home/ec2-user/.ssh/authorized_keys for user ec2-user+
ci-info: Keytype Fingerprint (md5) Options Comment
ci-info: ssh-rsa 7d:7f:10:0a:99:XXXXXXXXXXXXXXXXXXXXXXXXX- ATS-Nag
ec2:


Nagios-AMI System console Log
Enabling EPEL repo...
Installing EPEL PKG: ./packages/epel-release-6-8.noarch.rpm
warning: ./packages/epel-release-6-8.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY

Preparing... ##################################################
epel-release ##################################################
Loaded plugins: fastestmirror
Determining fastest mirrors
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
epel-release RPM installed OK

We have a current bug into our developers for this. It seems that upon install epel is forcing https, but those do not respond. Mounting the drive on another instance, correcting /etc/yum.repos.d/epel.repo to use http only, then restarting with the drive correctly attached will properly get your ssh keys once the XI install finishes.