Deployment Architecture

SmartStore configuration

oscar84x
Contributor

Hello everyone.

I'm testing a SmartStore configuration and I'm getting some errors when Splunk tries to move the buckets to the remote storage, which I suspect have to do with authentication. The endpoint provided to me is “<bucket_name>.s3-accesspoint.us-east-1.amazonaws.com" and I'm trying to confirm if I should be using http or https. The CacheManger and S3Client errors I'm getting are, using http "status=failed, reason="HTTP Error 307: Temporary Redirect"", and using https "status=failed, reason="HTTP Error 400: Bad Request""

This is my volume and index configuration. I was wondering if anyone could spot any obvious config errors or point me in the right direction.

 

[volume:s3]
storageType = remote
path = s3://<bucket_name>/
remote.s3.endpoint = https://<bucket_name>.s3-accesspoint.us-east-1.amazonaws.com
remote.s3.access_key = <access_key>
remote.s3.secret_key = <secret_key>

[smartstore_test]
remotePath = volume:s3/smartstore_test
##retention settings##
maxGlobalDataSizeMB = 0
#38 months
frozenTimePeriodInSecs = 99900000
repFactor = auto
homePath = $SPLUNK_DB/smartstore_test/db
thawedPath = $SPLUNK_DB/smartstore_test/thaweddb
coldPath = $SPLUNK_DB/smartstore_test/colddb

 

 

 

 

 

Labels (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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...