Glacier storage class is not supported – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when you’re trying to use Amazon S3’s Glacier storage class with Elasticsearch, which is not supported. Elasticsearch requires immediate access to data, but Glacier is designed for long-term archival storage with retrieval times that can take several hours. To resolve this issue, you can either change your S3 storage class to a class that provides immediate access, such as Standard, or configure a lifecycle policy to move data from Glacier to a supported class before Elasticsearch needs to access it.

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

Log Context

Log “Glacier storage class is not supported” class name 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.");


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?