Setting is set but and are not – 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 ” Setting is set but and are not ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-ec2, plugins and discovery.

Log Context

Log “Setting [{}] is set but [{}] and [{}] are not”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

try (SecureString key = ACCESS_KEY_SETTING.get(settings);
 SecureString secret = SECRET_KEY_SETTING.get(settings);
 SecureString sessionToken = SESSION_TOKEN_SETTING.get(settings)) {
 if (key.length() == 0 && secret.length() == 0) {
 if (sessionToken.length() > 0) {
 throw new SettingsException("Setting [{}] is set but [{}] and [{}] are not";
 logger.debug("Using either environment variables; system properties or instance profile credentials");
 return null;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content