All Apps and Add-ons

Splunk Add-on for Amazon Web Services: Getting “'NoneType' object has no attribute 'get_all_buckets'” error when trying to create any AWS S3 input

aitortilla
New Member

Hello team,

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
hand.execute(info)
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 [400]: 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 [400]: Bad Request -- 'NoneType' object has no attribute 'get_all_buckets'". See splunkd.log for more details.

Labels (1)
0 Karma
Get Updates on the Splunk Community!

Splunk Enterprise Security: Your Command Center for PCI DSS Compliance

Every security professional knows the drill. The PCI DSS audit is approaching, and suddenly everyone's asking ...

Developer Spotlight with Guilhem Marchand

From Splunk Engineer to Founder: The Journey Behind TrackMe    After spending over 12 years working full time ...

Cisco Catalyst Center Meets Splunk ITSI: From 'Payments Are Down' to Root Cause in ...

The Problem: When Networks and Services Don't Talk Payment systems fail at a retail location. Customers are ...