Open kubukoz opened 4 months ago
Got another one, with aws's Location service (needs #1592, #1594 to compile):
// sdk.listTrackers().debug().void
[E] java.net.UnknownHostException: cp.tracking.ListTrackers.us-east-1.amazonaws.com: nodename nor servname provided, or not known
A wild guess and a passing ping
tell me that it should be cp.tracking.geo.us-east-1.amazonaws.com
(geo
is the arnNamespace
for the location service, cp.tracking.
is the endpoint prefix of the ListTrackers operation).
With the Account api, it would be arnNamespace: account
and no prefix, so: account.us-east-1.amazonaws.com
(which pings successfully).
Applying a middleware as a workaround to use the correct host wasn't enough: I still get a Forbidden response.
The things that are different at the moment when we compare to the CLI:
X-Amz-Target
doesn't get sent in the CLI and isn't part of the signed headers list, I don't know if this is an issuehost
header matches the URI host, so they'll probably be fixed togetherCredential=<redacted>/20240927/us-east-1/locationservice/aws4_request
, CLI sends Credential=<redacted>/20240927/us-east-1/geo/aws4_request
.On a positive note, the security token is identical.
This seems to be resolvable by updating baseRequest
in AwsClient.scala
, however we then bump into #1568.
I made an early draft of a fix for both issues in #1596.
Version: 0.18.19
Build:
Exception: