Currently we are using the following endpoints to add AWS accounts in the Splunk AddOn for AWS: https://localhost:8089/servicesNS/nobody/Splunk_TA_aws/configs/conf-aws_account_ext https://localhost:8089/servicesNS/nobody/Splunk_TA_aws/storage/passwords We have a python script that goes out using Boto3 and requests Key Id and Secrete Access Key for our AWS user. We get those Keys and then we send them to both endpoints to add one of our AWS accounts to the Add on. When doing this it seems that if we get a Secrete Access Key that has a '/' or a '+' sign (special character) in the key the account creation does happen but then if we go so one of our Account Inputs like an S3 input we receive the following error: "An error occurred (SignatureDoesNotMatch) when calling the GetCallerIdentity operation: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.. Please make sure the AWS Account and Assume Role are correct." Now if I get a key that DOES NOT have a special character in it then it works fine. I have searched and I have not found a 100% fix for this anywhere, or what the proper way is to send a Key with special characters to the API endpoint in python. I am using the requests library. Does anyone have any suggestions? Any help will be MUCH appreciated. ... View more

We have a clustered environment, we have the Splunk Add On for Infoblox setup and configuered. We are getting the DNS Captures and the DHCP and DNS data from the logs over UDP port. This seems to be working fine. The other piece of this though is the actual syslog data. We are also trying to send that over UDP port, and we are not getting any of the syslog sourcetype data in splunk. Is there something special we have to do with splunk or infoblox? ... View more