Glacier storage class is not supported – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Glacier storage class is not supported ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, storage, repository-s3 and plugins.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Glacier storage class is not supported”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 try {
 final StorageClass _storageClass = StorageClass.fromValue(storageClass.toUpperCase(Locale.ENGLISH));
 if (_storageClass.equals(StorageClass.Glacier)) {
 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.");


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content