Skip to content

Location client stopped working with 2.18.0 #3517

Closed
@jankoh

Description

@jankoh

Describe the bug

Starting with 2.18.0, the location stopped working triggering the exception:

Received an UnknownHostException when attempting to interact with a service. See cause for the exact endpoint that is failing to resolve. If this is happening on an endpoint that previously worked, there may be a network connectivity issue or your DNS cache could be storing endpoints for too long.

Digging a bit into the problem, we found the cause to be reported as

software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: geo.eu-central-1.amazonaws.com

The main issue seems to be we have region (or AWS_REGION) set in the configuration, which we need to hav set to properly access AWS's S3. However, "geo.eu-central-1.amazonaws.com" simply does not exist.

Is there a change documented I have missed?

We simply initialise and use the client like that having set ~/.aws/credentials and a working S3 using that settings.

private val locationClient: LocationClient = LocationClient.builder().build()
...
locationClient.searchPlaceIndexForText("find my town")

Expected Behavior

LocationService should still work.

Current Behavior

LocationService should stopped working.

Reproduction Steps

Upgrade 2.17.X to 2.18.X (0,1, or 2)

Possible Solution

No response

Additional Information/Context

No response

AWS Java SDK version used

2.18.X

JDK version used

17.0.4

Operating System and version

Linux 5.19.0

Metadata

Metadata

Assignees

Labels

bugThis issue is a bug.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions