-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Remove either endpoint or region setting in aws cloud plugins #22758
Copy link
Copy link
Labels
:Distributed/Discovery-PluginsAnything related to our integration plugins with EC2, GCP and AzureAnything related to our integration plugins with EC2, GCP and Azure:Distributed/Snapshot/RestoreAnything directly related to the `_snapshot/*` APIsAnything directly related to the `_snapshot/*` APIshelp wantedadoptmeadoptme
Description
We have two different settings, endpoint and region, which determine the endpoint that is set on the aws client (and both of these appear unnecessary by default, as neither are required, and the s3 client appears to automatically find the region for a given bucket). My understanding is that it is useful to have an explicit setting to allow connecting to new regions without needing a new release. However, I don't think we need both settings? We should settle on one (I would think endpoint, and remove region altogether?).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Distributed/Discovery-PluginsAnything related to our integration plugins with EC2, GCP and AzureAnything related to our integration plugins with EC2, GCP and Azure:Distributed/Snapshot/RestoreAnything directly related to the `_snapshot/*` APIsAnything directly related to the `_snapshot/*` APIshelp wantedadoptmeadoptme
Type
Fields
Give feedbackNo fields configured for issues without a type.