Getting Data In

JSON files are not being onboarded intermittently via SQS based S3 input?

soumdey0192
Explorer

Hello All,

We have issue wherein JSON files are not coming in intermittently into Splunk from a SQS based S3 input.

The JSON file id generated everyday at 3 AM which is generally ingested into Splunk except for times when eventhough the file gets generated, but the file is not ingested on Splunk.

Unfortunately, there is no logs whatsoever generated on Splunk internal logs for times when the file is not ingested into Splunk.

Can anyone suggest what can be the issue here or if this has been encountered by someone?

The version of aws add-on being used here is, 5.0.4 and the Splunk version is 8.1.5.

Labels (2)
Tags (3)
0 Karma
Get Updates on the Splunk Community!

Splunk Search APIを使えば調査過程が残せます

   このゲストブログは、JCOM株式会社の情報セキュリティ本部・専任部長である渡辺慎太郎氏によって執筆されました。 Note: This article is published in both Japanese ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...