CannedACL is not valid cannedACL – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when the Access Control List (ACL) provided in the Elasticsearch request is not valid. The ACL, also known as cannedACL, is a predefined set of permissions for an object in Elasticsearch. To resolve this issue, you can check the cannedACL value you’re using and ensure it’s one of the predefined set by Elasticsearch. Also, ensure that the user has the necessary permissions to perform the operation. If the error persists, you may need to debug your code to identify any potential issues with the request.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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: repository-s3, repositories.

Log Context

Log “cannedACL is not valid: [” + cannedACL + “]” class name 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 + "]");
 }  ThreadPool getThreadPool() {
 return threadPool;


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?

Get expert answers on Elasticsearch/OpenSearch