All Apps and Add-ons

Splunk Add-on for Amazon Web Services: Why are fields appearing with Records{} prefix?

chanmic
New Member

Hi All,

I have installed the Splunk Add-on for AWS and I am able to ingest S3 logs into Splunk, but the dashboards are not working. When I look at the fields, I can see a lot of them are appearing with a pre-fix of Records{}. E.g., Records{}.requestID, Records{}.eventType etc...

I believe this is affecting the search. I don't see any errors in the log

Has anyone experienced this? I am hoping someone can point me to the right direction to fix it.

Cheers,
Michael.

0 Karma

jcoates_splunk
Splunk Employee
Splunk Employee

Hi, IIRC that's the format that you get from CloudTrail when there are multiple accounts writing into one bucket (http://docs.splunk.com/Documentation/AddOns/latest/AWS/ConfigureInputs#CloudTrail_inputs) -- newer versions of the Add-on should parse those records, but an older version would leave the records wrapper on.

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

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 ...