-
Notifications
You must be signed in to change notification settings - Fork 25.6k
S3 Repository: Remove region setting #22853
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
Conversation
This change removes the ability to set region for s3 repositories. Endpoint should be used instead if a custom s3 location needs to be used. closes elastic#22758
dadoonet
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good. I just wonder why we added support for s3.client.*.region in the first place.
I believe we should not introduce an already deprecated setting in the first place, no?
I was not sure what the feedback would be at the time on removing region, and chose to follow up separately. We could remove it from 5.x, since it has not been released yet. |
|
I see. Let's remove it then and change the doc then in this PR where we mention it. |
| to securely store the credentials. | ||
|
|
||
| * Specifying region has been removed. This includes the settings `cloud.aws.region`, | ||
| `cloud.aws.s3.region`, `repositories.s3.region`, `s3.client.*.region` and specifying |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So just remove here
,
s3.client.*.region
This change removes the ability to set region for s3 repositories.
Endpoint should be used instead if a custom s3 location needs to be
used.
closes #22758