Now this error seems to have got resolved, but still the connection configuration did not get through. Below is the error 06-09-2016 09:33:20.807 +0100 ERROR AdminManagerExternal - External handler failed with code '1' and output: 'Splunk Add-on REST Handler ERROR[400]: Bad Request - Splunkd daemon is not responding: ('Error connecting to /servicesNS/-/Splunk_TA_aws/storage/passwords/_aws_proxy%3Adefault%3A: [Errno 111] Connection refused',)'. See splunkd.log for stderr output. 06-09-2016 09:33:20.800 +0100 ERROR ScriptRunner - stderr from '/opt/splunk/bin/python /opt/splunk/bin/runScript.py execute': BaseException: Splunk Add-on REST Handler ERROR[400]: Bad Request - Splunkd daemon is not responding: ('Error connecting to /servicesNS/-/Splunk_TA_aws/storage/passwords/_aws_proxy%3Adefault%3A: [Errno 111] Connection refused',) ... View more

I am getting a response for the ping command. There is a proxy server which filters all traffic to this server, unsure why even internal calls are going through the proxy. This is the error at the end of the stack of errors i have posted above: File "/opt/splunk/etc/apps/Splunk_TA_aws/bin/splunktalib/httplib2/__init__.py", line 1060, in connect raise socket.error, msg error: [Errno 111] Connection refused ... View more