Getting Data In

AWS Add-on 6.3 errors with Generic S3 inputs

steveski
Explorer

We recently updated our AWS Add-on to version 6.3, after which all Generic S3 inputs stopped ingesting. 

Noticed the following error being repeated during every S3 API call.    "parse_csv_with_delimiter'"

The data within our s3 bucket was a tar or .gz extension with either json or xml format,  after the upgrade our previous AWS s3 inputs seemed to have defaulted to csv format.

Ended up recreating several  AWS Generic S3 inputs using a start date from when the Add-on was updated, which allowed the previous missed logs to ingest again.

You can run this search to determine if your system is having a similar issue.

index=_internal level=ERROR ErrorDetail="'parse_csv_with_delimiter'"

 

 

Labels (4)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...