https://community.splunk.com/t5/Getting-Data-In/AWS-Add-on-6-3-errors-with-Generic-S3-inputs/m-p/626871#M107644 <P>We recently updated our AWS Add-on to version 6.3, after which all Generic S3 inputs stopped ingesting.&nbsp;</P><P>Noticed the following error being repeated during every S3 API call.&nbsp;&nbsp;&nbsp; "parse_csv_with_delimiter'"</P><P>The data within our s3 bucket was a tar or .gz extension with either json or xml format,&nbsp; after the upgrade our previous AWS s3 inputs seemed to have defaulted to csv format.</P><P>Ended up recreating several&nbsp; AWS Generic S3 inputs using a start date from when the Add-on was updated, which allowed the previous missed logs to ingest again.</P><P>You can run this search to determine if your system is having a similar issue.</P><P>index=_internal level=ERROR ErrorDetail="'parse_csv_with_delimiter'"</P><P>&nbsp;</P><P>&nbsp;</P> Wed, 11 Jan 2023 22:45:08 GMT steveski 2023-01-11T22:45:08Z https://community.splunk.com/t5/Getting-Data-In/AWS-Add-on-6-3-errors-with-Generic-S3-inputs/m-p/626871#M107644 <P>We recently updated our AWS Add-on to version 6.3, after which all Generic S3 inputs stopped ingesting.&nbsp;</P><P>Noticed the following error being repeated during every S3 API call.&nbsp;&nbsp;&nbsp; "parse_csv_with_delimiter'"</P><P>The data within our s3 bucket was a tar or .gz extension with either json or xml format,&nbsp; after the upgrade our previous AWS s3 inputs seemed to have defaulted to csv format.</P><P>Ended up recreating several&nbsp; AWS Generic S3 inputs using a start date from when the Add-on was updated, which allowed the previous missed logs to ingest again.</P><P>You can run this search to determine if your system is having a similar issue.</P><P>index=_internal level=ERROR ErrorDetail="'parse_csv_with_delimiter'"</P><P>&nbsp;</P><P>&nbsp;</P> Wed, 11 Jan 2023 22:45:08 GMT https://community.splunk.com/t5/Getting-Data-In/AWS-Add-on-6-3-errors-with-Generic-S3-inputs/m-p/626871#M107644 steveski 2023-01-11T22:45:08Z