All Apps and Add-ons

While trying to set up Splunk using an AMI provided by the AWS marketplace, why is it failing to create a virtual index connection?

New Member


I'm new to this setup. I used an AMI provided by AWS marketplace for splunk setup.
i created an EMR in AWS and provided details in emr-provider(internal IP of master node:9001 ) for job tracker (since created both server in same subnet)

While creating a virtual index, I provided data in HDFS as (bucket name where elb logs reside with access_id and secret key), but I'm getting this error:

[emr-provider] Error while running external process, return_code=255. See search.log for more info

[emr-provider] RuntimeException - Failed to create a virtual index filesystem connection: AWS Access Key ID and Secret Access Key must be specified as the username or password (respectively) of a s3 URL, or by setting the fs.s3.awsAccessKeyId or fs.s3.awsSecretAccessKey properties (respectively).. Advice: Verify that your is correct and available.

Now I am not able to understand where the problem is. Please help me to sort out this problem.

0 Karma

Splunk Employee
Splunk Employee

When using AWS our recommendation is to use the OEM/hourly integration which takes care of a lot of the underlying auth issues - more info here and here

Regarding the error message you're seeing it's basically telling you that we cannot connect to S3 to fetch the data. To solve that you need to do one of the following:

a. provide credentials in the vix path (notice using s3n instead of s3)
input path: s3n://[awsAccessKeyId]:[awsSecretAccessKey]@bucket_name/path/to/data

b. provide the credentials in the provider via "Additional settings":

vix.fs.s3n.awsAccessKeyId = 
vix.fs.s3n.awsSecretAccessKey = 

then in your vix input path use s3n://bucket_name/path/to/data
0 Karma
.conf21 CFS Extended through 5/20!

Don't miss your chance
to share your Splunk
wisdom in-person or
virtually at .conf21!

Call for Speakers has
been extended through
Thursday, 5/20!