Has anyone had any success with the Amazon EC2 discovery wizard? I enter my secrets and access key and it doesn't find any targets, I know my keys are valid as I'm using them with aws cli and eb cli. I've also tried setting it up locally on the NagiosXI server in flat files with no success.
Any help would be appreciated
Michael
Amazon EC2 Issue
Re: Amazon EC2 Issue
Hi Michael,
How are you doing?
Here's the KB article I found on how to setup and monitor EC2:
https://www.orb-data.com/amazon-ec2-mon ... nagios-xi/
Do you have internet connection on your XI machine (VM)?
See if you can ping "aws.amazon.com" from your XI machine.
Also see if "sshd" is running on your XI machine (VM) as well.
Best Regards,
Vinh
How are you doing?
Here's the KB article I found on how to setup and monitor EC2:
https://www.orb-data.com/amazon-ec2-mon ... nagios-xi/
Do you have internet connection on your XI machine (VM)?
See if you can ping "aws.amazon.com" from your XI machine.
Code: Select all
ping aws.amazon.comCode: Select all
systemctl status sshdBest Regards,
Vinh
Re: Amazon EC2 Issue
Thanks Vinh,
I have confirmed that I can ping aws.amazon.com and that sshd is running on the the XI host. I went in a created the credentials following the tutorial, but when I hit get instances it tells me "There were no instances found. Verify your AWS credentials and try again." My NagiosXI vm is sitting in the same vpc as the rest of my vm's
I have confirmed that I can ping aws.amazon.com and that sshd is running on the the XI host. I went in a created the credentials following the tutorial, but when I hit get instances it tells me "There were no instances found. Verify your AWS credentials and try again." My NagiosXI vm is sitting in the same vpc as the rest of my vm's
Re: Amazon EC2 Issue
Hi Michael,
How are you doing?
I tested the EC2 wizard and looks like it is working for me.
Could you please try and see if you can ping the public IP of that EC2 instance?
Also, could you please check the security settings for "inbound" of SSH like "port" and "allowed IP"?
Please upload screenshot if possible ...
Best Regards,
Vinh
How are you doing?
I tested the EC2 wizard and looks like it is working for me.
Could you please try and see if you can ping the public IP of that EC2 instance?
Also, could you please check the security settings for "inbound" of SSH like "port" and "allowed IP"?
Please upload screenshot if possible ...
Best Regards,
Vinh
You do not have the required permissions to view the files attached to this post.
Re: Amazon EC2 Issue
Thanks Vinh,
That may have been part of the problem I did open all ec2s to ping and ssh from the nagiosxi server within my security group, currently everything is being monitored across the private ip's
--- 18.221.20.222 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 28ms
rtt min/avg/max/mdev = 1.245/1.299/1.352/0.035 ms
[nagios@nagiosxi libexec]$ ssh 18.221.20.222
The authenticity of host '18.221.20.222 (18.221.20.222)' can't be established.
ECDSA key fingerprint is SHA256:SEVttmB/+lFOz96nb9xkaXrNnF5QcEfWJ53KpFHhJ2k.
Are you sure you want to continue connecting (yes/no/[fingerprint])? ^C
[nagios@nagiosxi libexec]$ ping 18.221.20.222
PING 18.221.20.222 (18.221.20.222) 56(84) bytes of data.
64 bytes from 18.221.20.222: icmp_seq=1 ttl=254 time=1.23 ms
64 bytes from 18.221.20.222: icmp_seq=2 ttl=254 time=1.27 ms
64 bytes from 18.221.20.222: icmp_seq=3 ttl=254 time=1.38 ms
64 bytes from 18.221.20.222: icmp_seq=4 ttl=254 time=1.29 ms
^C
--- 18.221.20.222 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 6ms
rtt min/avg/max/mdev = 1.234/1.294/1.380/0.059 ms
when I try and troubleshoot from the command line I'm getting a weird error like there may be a bug in the script or my env isn't setup properly. It did ask me to install boto3 initially which I completed.
[nagios@nagiosxi libexec]$ ./check_ec2.py -k blahblahblahblah -K blahblahblahblah -g -v
File "./check_ec2.py", line 176
print instance_list
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(instance_list)?
That may have been part of the problem I did open all ec2s to ping and ssh from the nagiosxi server within my security group, currently everything is being monitored across the private ip's
--- 18.221.20.222 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 28ms
rtt min/avg/max/mdev = 1.245/1.299/1.352/0.035 ms
[nagios@nagiosxi libexec]$ ssh 18.221.20.222
The authenticity of host '18.221.20.222 (18.221.20.222)' can't be established.
ECDSA key fingerprint is SHA256:SEVttmB/+lFOz96nb9xkaXrNnF5QcEfWJ53KpFHhJ2k.
Are you sure you want to continue connecting (yes/no/[fingerprint])? ^C
[nagios@nagiosxi libexec]$ ping 18.221.20.222
PING 18.221.20.222 (18.221.20.222) 56(84) bytes of data.
64 bytes from 18.221.20.222: icmp_seq=1 ttl=254 time=1.23 ms
64 bytes from 18.221.20.222: icmp_seq=2 ttl=254 time=1.27 ms
64 bytes from 18.221.20.222: icmp_seq=3 ttl=254 time=1.38 ms
64 bytes from 18.221.20.222: icmp_seq=4 ttl=254 time=1.29 ms
^C
--- 18.221.20.222 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 6ms
rtt min/avg/max/mdev = 1.234/1.294/1.380/0.059 ms
when I try and troubleshoot from the command line I'm getting a weird error like there may be a bug in the script or my env isn't setup properly. It did ask me to install boto3 initially which I completed.
[nagios@nagiosxi libexec]$ ./check_ec2.py -k blahblahblahblah -K blahblahblahblah -g -v
File "./check_ec2.py", line 176
print instance_list
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(instance_list)?
Re: Amazon EC2 Issue
Hi,
Can you please share the screenshot of your AWS EC2 security settings for SSH?
Here's the command in my test earlier: You might have to talk to your Network admin group for helps.
Best Regards,
Vinh
Can you please share the screenshot of your AWS EC2 security settings for SSH?
Here's the command in my test earlier: You might have to talk to your Network admin group for helps.
Best Regards,
Vinh
You do not have the required permissions to view the files attached to this post.