Neither a secret key nor a shared access token was set. – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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: repositories, azure, repository-azure and plugins.

Log Context

Log “Neither a secret key nor a shared access token was set.”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

private static String buildConnectString(String account; @Nullable String key; @Nullable String sasToken; String endpointSuffix) {
 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();


See how you can use AutoOps to resolve issues

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Analyze your cluster & get personalized recommendations

Skip to content