Join the Conversation
- Find Answers
- :
- Apps & Add-ons
- :
- All Apps and Add-ons
- :
- Re: AWS Error -> ClientError: An error occurred (U...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Resolve AWS Error:ClientError: An error occurred (UnsupportedArgument) when calling the GetBucketAccelerateConfiguration
Hello Folks,
Some of my inputs are generating the following error:
"ClientError: An error occurred (UnsupportedArgument) when calling the GetBucketAccelerateConfiguration operation: The request contained an unsupported argument."
Has anyone experienced such error? Any tips on how to solve it?
Let me know if more details are needed...
Thank you!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the same issue. Did you ever find the cause?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting this as well, and assume it's because S3 Transfer Acceleration is not available in GovCloud. I'm going to open a support case about it, since I think the app should gracefully handle that.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@dbarrpsu Was there a specific case/bug that they attributed this to?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, an enhancement request was filed, ENH-6668. Jumping on with your own case may help bump the priority.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IMO, this should be treated as a bug and not an enhancement request. I still see this error in AWS add-on ver 6.2.0.
Unlock Database Monitoring with Splunk Observability Cloud
Purpose in Action: How Splunk Is Helping Power an Inclusive Future for All
[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk
