-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'us-east-1` is not a valid region when creating s3 bucket #16978
Comments
As per http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUT.html: "If you are creating a bucket on the US East (N. Virginia) region (us-east-1), you do not need to specify the location constraint". Other regions work fine. I can take this up. |
Knowing that we deprecated @clintongormley WDYT? |
This issue wasn't even about region really, it was about auto bucket creation (failing because of specifying region). Since auto bucket creation is now gone, we can close. |
Thanks @rjernst |
Elasticsearch version: master
JVM version: 1.8
OS version: OSX
Describe the feature:
When we using
us-east-1
, s3 plugin will first get the endpoint by using theregion
, and then use the endpoint to create the client, this is fine.But when creating the bucket, s3 plugin will will the
bucket
name to build aCreateBucketRequest
(link),us-east-1
is not valid for aws s3 sdk.Reproduce:
Succeed after removed the region
Same thing happened if we used
us-west
|ap-southeast
|eu-central
...I think if we could get the endpoint, we should using the valid region name and let user be able to create buckets.
The text was updated successfully, but these errors were encountered: