Splunk Search

Data Input not working for s3 plugin -- perhaps inputs.conf.spec is wrong?

boris
Path Finder

File /opt/splunk/etc/apps/s3/README/inputs.conf.spec:

[s3://umi-mf-cdnlogs]

key_id = AKIA

secret_key = EOW5NUqjoJalt text

~

~

Tags (1)

khourihan_splun
Splunk Employee
Splunk Employee

does that bucket have a contain called tiles-cdn?

I've got an input for cloudfront:

[s3://freesoft001]
key_id = AKIA
# This is Amazon key ID.
secret_key = riuvl
# This is the secret key.
sourcetype=freesoft_cloudfront

which captures my S3 logs no problem. freesoft001 has a container called cloud-front, and Splunk successfully traverses down into it, but it doesn't show up on my inputs screen.

alt text

0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...