Splunk Enterprise

How to forward the data from AWS S3 to Splunk Enterprise?

akarivaratharaj
Communicator

I have installed a free version of Splunk Enterprise 9.1 in my local system. I would need few logs files from my S3 bucket to be sent to Splunk.

I have setup up the Splunk Add-on for AWS. In the app, under configuration, created an account with access ID and secret access key. Then created an input by specifying the account name, bucket name and indexing details.

After creating the input, when I search my index and sourcetype, I could not find the logs from S3. I have waited for more than half an hour, then tried again but no luck.

As this is the first time I am trying the setup with AWS add-on, I am not sure whether the issue is happening. Could anyone please help me on this?

Labels (2)
Tags (1)
0 Karma

akarivaratharaj
Communicator

I am curious to know about a couple of things related to fetching S3 logs.

  • Is there any limitation in the number of inputs which we create in the AWS add-on?
  • Is there any limitation on indexes on which we log the S3 data?
0 Karma

akarivaratharaj
Communicator

Yes, there was some error with endpoint. I have checked the error via below query

index=_internal sourcetype=aws:s3:log ERROR
0 Karma

thahir
Path Finder

Please check the aws s3 logs in the splunk end it may be due to permission issue from aws end. Once you go through the logs you will get clear visibility.  the logs will be under /opt/splunk/var/log/splunk and serach for aws.

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...