Hi All,
Does the AWS SQS Poller app support Proxy server option like SPLUNK Add-on for AWS?
The SQS Poller data input does not provide an option to configure proxy server, but is there a way we can change it in the background and run it which will connect to proxy server and then to AWS API?
Initially we were going with Add-on for AWS, but looks like the add-on cannot consume messages from SQS if it is not coming from Cloudtrail or Config -> SNS --> SQS.
Regards,
Badri
@badrinath_it,
As it currently been written no, but it relatively simple enhancement. This App was written for an internal process at my company and at this time I do not plan on adding a configurable proxy setting. Though I am scheduled to do some maintenance on the module in the next coming months, feel free to add an enhancement request @ https://github.com/httpstergeek/splunk-sqs/issues. If you need this now run npm install proxy-agent --save in the $APP$/bin/app_dr @ line 134 in sqs_poller.js:
var proxy = require('proxy-agent');
aws.config.update({
httpOptions: { agent: proxy('$YOUR_PROXY$') }
});
You might have to play around a bit or look at the proxy-agent documentation. Probably not what you wanted to here. Its open on git to be forked. Cheers
@badrinath_it,
As it currently been written no, but it relatively simple enhancement. This App was written for an internal process at my company and at this time I do not plan on adding a configurable proxy setting. Though I am scheduled to do some maintenance on the module in the next coming months, feel free to add an enhancement request @ https://github.com/httpstergeek/splunk-sqs/issues. If you need this now run npm install proxy-agent --save in the $APP$/bin/app_dr @ line 134 in sqs_poller.js:
var proxy = require('proxy-agent');
aws.config.update({
httpOptions: { agent: proxy('$YOUR_PROXY$') }
});
You might have to play around a bit or look at the proxy-agent documentation. Probably not what you wanted to here. Its open on git to be forked. Cheers
Thank you !! Let modify the code and see if that works for us as well.
I have also added this request as an enhancement in github.
@bmacias84,
Thank you !! modified the code as per your suggestion and guideline provided in below AWS blog.
Solved the Problem .