Api keys are not enabled – How to solve this Elasticsearch error

Average Read Time

2 Mins

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” api keys are not enabled ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 {


Run the Check-Up to get a customized report like this:

Analyze your cluster