No bucket defined for s3 repository – Elasticsearch Error How To Solve Related Issues

No bucket defined for s3 repository – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “No bucket defined for s3 repository” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: repositories, repository-s3, repository, plugins.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”No bucket defined for s3 repository”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

this.service = service;
  // Parse and validate the user's S3 Storage Class setting
  this.bucket = BUCKET_SETTING.get(metadata.settings());
  if (bucket == null) {
  throw new RepositoryException(; "No bucket defined for s3 repository");
  this.bufferSize = BUFFER_SIZE_SETTING.get(metadata.settings());
  this.chunkSize = CHUNK_SIZE_SETTING.get(metadata.settings());


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Can I define a snapshot repository in the configuration YAML? -views 736 

Restoring indices from snapshot to a test server – Elasticsearch …  



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now