You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ran into an issue using AWS Location Service. It seems that is uses a slightly different endpoint setup than other services. It has sub-services that need to be prepended onto the base region endpoint: https://docs.aws.amazon.com/general/latest/gr/location.html
I looked at endpoints.json, and it doesn’t appear to include any detail for geo below the regional level. So I’m not sure there’s a good way for aws-api to fix this without introducing a special case.
I just wanted to note this here in case anyone else runs into the issue.
The simple fix is to override the endpoint depending on which sub-service you need:
Ran into an issue using AWS Location Service. It seems that is uses a slightly different endpoint setup than other services. It has sub-services that need to be prepended onto the base region endpoint: https://docs.aws.amazon.com/general/latest/gr/location.html
I looked at
endpoints.json
, and it doesn’t appear to include any detail forgeo
below the regional level. So I’m not sure there’s a good way foraws-api
to fix this without introducing a special case.I just wanted to note this here in case anyone else runs into the issue.
The simple fix is to override the endpoint depending on which sub-service you need:
Dependencies
The text was updated successfully, but these errors were encountered: