StorageClass is not a valid S3 Storage Class – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the specified S3 storage class in Elasticsearch snapshot repository configuration is not recognized by AWS. The storage class could be misspelled or not supported. To resolve this issue, ensure that the storage class is one of the following: STANDARD, REDUCED_REDUNDANCY, STANDARD_IA, ONEZONE_IA, INTELLIGENT_TIERING, GLACIER, or DEEP_ARCHIVE. Also, check for any typographical errors in the storage class name.

This guide will help you check for common problems that cause the log ” `” + storageClass + “` is not a valid S3 Storage Class. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository-s3, storage, repositories.

Log Context

Log “`” + storageClass + “` is not a valid S3 Storage Class.” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new BlobStoreException("Glacier storage class is not supported");
 }  return _storageClass;
 } catch (final IllegalArgumentException illegalArgumentException) {
 throw new BlobStoreException("`" + storageClass + "` is not a valid S3 Storage Class.");
 }  /**
 * Constructs canned acl from string


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?