CannedACL is not valid: ” + cannedACL + ” – 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 ” cannedACL is not valid: ” + cannedACL + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, repository-s3 and plugins.

Log Context

Log “cannedACL is not valid: [” + cannedACL + “]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (cur.toString().equalsIgnoreCase(cannedACL)) {
 return cur;
 throw new BlobStoreException("cannedACL is not valid: [" + cannedACL + "]");
 static class Stats { 
 final AtomicLong listCount = new AtomicLong();


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content