Briefly, this error occurs when Elasticsearch is unable to authenticate a request due to missing security credentials. It’s expecting either a secret key or a shared access token, but neither has been provided. To resolve this issue, you can either set a secret key or a shared access token in your Elasticsearch configuration. Ensure that the credentials are correct and have the necessary permissions. If you’re using an access token, make sure it hasn’t expired. Also, check your application’s code to ensure it’s correctly passing these credentials when making requests to Elasticsearch.
This guide will help you check for common problems that cause the log ” Neither a secret key nor a shared access token was set. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: azure, repository-azure, repositories.
Overview
An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read snapshot for more information). The backup process requires a repository to be created first. The repository needs to be registered using the _snapshot endpoint, and multiple repositories can be created per cluster. The following repository types are supported:
Repository types
| Repository type | Configuration type |
|---|---|
| Shared file system | Type: “fs” |
| S3 | Type : “s3” |
| HDFS | Type :“hdfs” |
| Azure | Type: “azure” |
| Google Cloud Storage | Type : “gcs” |
Examples
To register an “fs” repository:
PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
}
}Notes and good things to know
- S3, HDFS, Azure and Google Cloud require a relevant plugin to be installed before it can be used for a snapshot.
- The setting, path.repo: /mnt/my_repo_dir needs to be added to elasticsearch.yml on all the nodes if you are planning to use the repo type of file system. Otherwise, it will fail.
- When using remote repositories, the network bandwidth and repository storage throughput should be high enough to complete the snapshot operations normally, otherwise you will end up with partial snapshots.
Log Context
Log “Neither a secret key nor a shared access token was set.” class name is AzureStorageSettings.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
@Nullable String secondaryEndpoint
) {
final boolean hasSasToken = Strings.hasText(sasToken);
final boolean hasKey = Strings.hasText(key);
if (hasSasToken == false && hasKey == false) {
throw new SettingsException("Neither a secret key nor a shared access token was set.");
}
if (hasSasToken && hasKey) {
throw new SettingsException("Both a secret as well as a shared access token were set.");
}
final StringBuilder connectionStringBuilder = new StringBuilder();
