Configure the Azure Blob 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 Azure Blob storage, Google GCS and AWS S3,. For information on S3, see Configure the S3 remote store for SmartStore. For information on GCS, see Configure the GCS remote store for SmartStore.
Configure an Azure Blob remote store
When configuring Azure Blob storage containers:
- The indexers' Azure service account must have read, write and delete permissions for the container that the indexers are associated with.
- The container must run in the same Azure region as the indexer instances.
See the Microsoft Azure documentation for information on on how to create and configure containers.
For Azure-specific settings available through Splunk Enterprise, search for settings in the indexes.conf spec file that start with remote.azure
.
For information on security-related settings, such as settings for Azure Blob storage authentication and encryption, see SmartStore on Azure Blob security strategies.
Configure the GCS remote store for SmartStore | Choose the storage location for each index |
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, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.3.0, 9.3.1
Feedback submitted, thanks!