Api keys are not enabled – 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.

Briefly, this error occurs when attempting to use the Elasticsearch API keys feature, which provides a way to securely authenticate and authorize API requests. If API keys are not enabled, then Elasticsearch cannot verify the identity or permissions of the requester. To resolve the issue, you can try enabling API keys in the Elasticsearch configuration or settings, and creating and using API keys to authenticate and authorize requests.

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 ” api keys are not enabled ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “api keys are not enabled”classname  is ApiKeyService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (licenseState.isSecurityEnabled() == false ||
 licenseState.checkFeature(XPackLicenseState.Feature.SECURITY_API_KEY_SERVICE) == false) {
 throw LicenseUtils.newComplianceException("api keys");
 if (enabled == false) {
 throw new FeatureNotEnabledException(Feature.API_KEY_SERVICE; "api keys are not enabled");
 // package private class for testing
 static final class ApiKeyCredentials implements Closeable {


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