Open clintongormley opened 9 years ago
Indeed. In documentation we wrote that if no region is provided we fallback to default US region.
Wondering if we should really support region: ""
. Why providing the region in that case?
If we do that, we should also support it for ec2 regions.
@tlrx WDYT?
Using "region": "us-standard"
doesn't work as well.
{
"error":"RemoteTransportException[[Bushmaster][inet[/x.x.x.x:9300]][cluster:admin/repository/put]]; nested: RepositoryException[[elk_repository] failed to create repository]; nested: CreationException[Guice creation errors:\n\n1) Error injecting constructor, org.elasticsearch.ElasticsearchIllegalArgumentException: No automatic endpoint could be derived from region [us-standard]\n at org.elasticsearch.repositories.s3.S3Repository.<init>()\n at org.elasticsearch.repositories.s3.S3Repository\n at Key[type=org.elasticsearch.repositories.Repository, annotation=[none]]\n\n1 error]; nested: ElasticsearchIllegalArgumentException[No automatic endpoint could be derived from region [us-standard]]; ",
"status":500
}
FIXED
"region": "us-east-1"
According to AWS S3 documentation http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGETlocation.html the empty string is used for create buckets in the US classic region. But configuring an empty region in the snapshot raises this error in elasticsearch:
org.elasticsearch.ElasticsearchIllegalArgumentException: No automatic endpoint could be derived from region []
us-east-1 can't be used because then AWS raise this error: The specified location-constraint is not valid (Service: Amazon S3; Status Code: 400; Error Code: InvalidLocationConstraint
(Opened from https://github.com/elasticsearch/elasticsearch/issues/9202)