I have been always getting this error on the new input configuration just after selecting the AWS Account (which I could configure successfully before). Because of this I cannot select the S3 Bucket.
I have tried this configuration with 8.0.3 Splunk Enterprise + 5.0.1 AWS Add-On and 8.0.4 Splunk Enterprise + 5.0.1 AWS Add-On without success so far.
This is the error logged in splunkd:
05-27-2020 10:21:02.050 +0200 ERROR AdminManagerExternal - Stack trace from python handler:
Traceback (most recent call last):
File "/opt/splunk/lib/python3.7/site-packages/splunk/admin.py", line 148, in init
File "/opt/splunk/lib/python3.7/site-packages/splunk/admin.py", line 634, in execute\n if self.requestedAction == ACTION_LIST: self.handleList(confInfo)\n File "", line 94, in handleList
File "", line 44, in timed
splunktaucclib.rest_handler.error.RestError: REST Error : Bad Request -- 'NoneType' object has no attribute 'get_all_buckets'
05-27-2020 10:21:02.050 +0200 ERROR AdminManagerExternal - Unexpected error "" from python handler: "REST Error : Bad Request -- 'NoneType' object has no attribute 'get_all_buckets'". See splunkd.log for more details.
... View more
As the Alert Manager Add-on was updated only a few days ago and is compatible with Splunk Cloud 8.0.x, I was wondering if this app is known to be updated for compatibility before running obsolete on August 1st
... View more