Configure the GCS remote store for SmartStore
Before you configure SmartStore settings on the indexers, you must ensure that your remote store is properly set up, so that it is available to the indexers.
Later, when you configure remote volumes for SmartStore, you configure settings specific to the remote store in
indexes.conf. The indexer uses those settings to communicate with the remote store.
Supported remote storage services
Supported remote storage services include GCS, AWS S3, and Microsoft Azure Blob storage. For information on S3, see Configure the S3 remote store for SmartStore. For information on Azure Blob storage, see Configure the Azure Blob remote store for SmartStore
Configure a GCS remote store
When configuring GCS buckets:
- The indexers' Compute Engine service account must have read, write and delete permissions for the GCS buckets that the indexers are associated with..
- Provision the buckets to run in the same GCP region as the indexer Compute Engine instances.
See the Google GCS documentation for information on on how to create and configure buckets.
For GCS-specific settings available through Splunk Enterprise, search for settings in the indexes.conf spec file that start with
For information on security-related settings, such as settings for GCS authentication and encryption, see SmartStore on GCS security strategies.
Configure the S3 remote store for SmartStore
Configure the Azure Blob remote store for SmartStore
This documentation applies to the following versions of Splunk® Enterprise: 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5
Feedback submitted, thanks!