All Apps and Add-ons

Only Partial AWS Config Data Indexed

JamesM
New Member
Within Splunk Enterprise 7.3.3 we are using AWS App,  and  the Add-on (4.6.1) mostly successfully. Several inputs work just fine with no issues.
Recently we noticed that the "aws:config" snapshot data is only being partially indexed. 
Dumbed down with example numbers:
  •   We have 20 Lambdas visible in both AWS Console site and  AWS:description type in Splunk.
  •   15 show up in sourcetype aws:config even after forcing new snapshot.
  •   Through trial and error we modified the tags on one and it suddenly showed up. We also confirmed through debug that the API response is returning said missing Lambdas, they are just not indexed/searchable.
Is there a set of qualifications/conditions the aws:config input type is filtering the response through before fully indexing? i.e. age of item, last modified, etc.? Any other input or suggestions on forcing all items to be searchable for aws:config sourcetype would be helpful. The aws:description input does not include some fields that we are trying to report on.
Labels (1)
Tags (1)
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!

A Four-Part Event Series: Full Stack Observability For the AI Era

As AI reshapes applications, infrastructure, and the way teams operate, the traditional boundaries of ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...