Search found 4 matches
- Tue Oct 20, 2015 2:43 am
- Forum: Nagios XI
- Topic: AWS boto3 cannot see credentials or $USER macros
- Replies: 5
- Views: 1442
Re: AWS boto3 cannot see credentials or $USER macros
There is not currently an option to disable the Test Check Command button, but I have mentioned a few times in the past that we should add some wording that the results are not always 100% accurate. That being said, is everything sorted out now? If so I would like to close the thread. yep, all work...
- Mon Oct 19, 2015 10:57 am
- Forum: Nagios XI
- Topic: AWS boto3 cannot see credentials or $USER macros
- Replies: 5
- Views: 1442
Re: AWS boto3 cannot see credentials or $USER macros
Here is the working script as in use now. To call it set $USERn$ variables as outlined above (for example to $USER9$ and $USER10$) and set the command up as $USER1$/check_ec2_statuscheck.py $ARG1$ and the service $ARG1$ as -u $USER9$ -a $USER10$ #!/usr/bin/python import boto3 import sys import os im...
- Mon Oct 19, 2015 10:39 am
- Forum: Nagios XI
- Topic: AWS boto3 cannot see credentials or $USER macros
- Replies: 5
- Views: 1442
Re: AWS boto3 cannot see credentials or $USER macros
A few things to note: 1.) Plugins are run by the nagios user during normal execution. Any command-line testing should be done as the nagios user to ensure accuracy of results. 2.) Judging by the output, you are using the "Test Check Command" button - this is good for simple tests but it d...
- Thu Oct 15, 2015 3:46 am
- Forum: Nagios XI
- Topic: AWS boto3 cannot see credentials or $USER macros
- Replies: 5
- Views: 1442
AWS boto3 cannot see credentials or $USER macros
I have written a python boto script to get some metric statistics from the AWS hosts in our production account The script uses AWS API calls to see which hosts are up and then asks each one for it's "StatusCheckFailed" stats. These represent health checks that AWS carry out on the VMs and ...