location service: dial tcp: lookup geo.us-east-1.amazonaws.com: no such host

[jaanauati]

Documentation

• I've gone though the API reference
• I've checked AWS Forums and StackOverflow for answers
• I've searched for previous similar issues and didn't find any solution

Describe the bug

Looks like the geo endpoints are wrongly configured to point to geo.{region}.amazonws.com, which leads to the following error:

operation error Location: DescribePlaceIndex, exceeded maximum number of attempts, 3, https response error StatusCode: 0, RequestID: , request send failed, Get "https://geo.us-east-1.amazonaws.com/places/v0/indexes/my-place-index": dial tcp: lookup geo.us-east-1.amazonaws.com: no such host

After spending some time poking with aws cli (using --debug flag) I found that the actual endpoint for this case should be:
https://places.geo.us-east-1.amazonaws.com (or maps.geo.{region}.amazonaws.com for the case of maps).

https://github.com/aws/aws-sdk-go-v2/blob/main/service/location/internal/endpoints/endpoints.go#L130

Btw, In case that someone else runs into this same issue, I'm currently using the following workaround, which seems to work well:

	configureUrlResolver := func(options *location.Options) {
		resolver := location.EndpointResolverFromURL("https://places.geo.us-east-1.amazonaws.com")
		options.EndpointResolver = resolver
	}
	location_client := location.NewFromConfig(cfg, configureUrlResolver)

Expected behavior

CreatePlaceIndexInput, DescribePlaceIndex, UpdatePlaceIndexInput, and DeletePlaceIndex functions should be able to create, describe, update and delete place index resources.

Current behavior

CreatePlaceIndexInput, DescribePlaceIndex, UpdatePlaceIndexInput, and DeletePlaceIndex functions return the following error:

operation error Location: DescribePlaceIndex, exceeded maximum number of attempts, 3, https response error StatusCode: 0, RequestID: , request send failed, Get "https://geo.us-east-1.amazonaws.com/places/v0/indexes/my-place-index": dial tcp: lookup geo.us-east-1.amazonaws.com: no such host

Steps to Reproduce

	ctx := context.TODO()
	cfg, err := config.LoadDefaultConfig(ctx)
	if err != nil {
		log.Fatal(err)
		return err
	}
	location_client := location.NewFromConfig(cfg)
        indexName := "my-awesome-index"
	details, err := location_client.DescribePlaceIndex(ctx, &location.DescribePlaceIndexInput{IndexName: &indexName})

Possible Solution

maybe including some additional endpoints or adding support for an additional param like: "{resourceType}."geo.{region}.amazonaws.com"

https://github.com/aws/aws-sdk-go-v2/blob/main/service/location/internal/endpoints/endpoints.go#L130

AWS Go SDK version used

v1.11.0

Compiler and Version used

go version go1.16.3 darwin/amd64

Operating System and version

macos 11.4

[skmcgrail]

Thanks for raising this issue @jaanauati, this appears to be a code-generation bug in our operation serializer. The host prefixes like places., tracking., etc. are to be sourced from the model to augment the resolved endpoint. We will need to investigate why our current code-generation logic is not handling this correctly.

[karl-dau]

I am facing the same problem, but can't get the workaround to work:

ctx := context.TODO()
cfg, err := config.LoadDefaultConfig(ctx)
if err != nil {
	panic(err)
}

configureUrlResolver := func(options *location.Options) {
    options.EndpointResolver = location.EndpointResolverFromURL("https://tracking.geo.eu-central-1.amazonaws.com")
}
locserv := location.NewFromConfig(cfg, configureUrlResolver)
trackerName := "MyFirstTracker"
out, err := locserv.DescribeTracker(ctx, &location.DescribeTrackerInput{
	TrackerName: &trackerName,
})
if err != nil {
	panic(err)
}

Panics with:

operation error Location: DescribeTracker, https response error StatusCode: 403, RequestID: <redacted>, api error MissingAuthenticationTokenException: Missing Authentication Token

Credentials seems fine (aws cli location works) and I wrote a basic Python program that does the same using boto3 and it works fine.

[jaanauati]

Hi., yes , i did face that same error w the describe-place operation, I made this fix: #1500 the rest of the operation seem to work well for me. El El jue, 25 nov. 2021 a la(s) 12:47, Karl Möller ***@***.***> escribió:

…

I am facing the same problem, but can't get the workaround to work: cfg, err := config.LoadDefaultConfig(context.Background()) if err != nil { panic(err) } configureUrlResolver := func(options *location.Options) { options.EndpointResolver = location.EndpointResolverFromURL(" https://tracking.geo.eu-central-1.amazonaws.com") } locserv := location.NewFromConfig(cfg, configureUrlResolver) trackerName := "MyFirstTracker" out, err := locserv.DescribeTracker(context.TODO(), &location.DescribeTrackerInput{ TrackerName: &trackerName, }) if err != nil { panic(err) } Panics with: operation error Location: DescribeTracker, https response error StatusCode: 403, RequestID: <redacted>, api error MissingAuthenticationTokenException: Missing Authentication Token Credentials seems fine (aws cli location works) and I wrote a basic Python program that does the same using boto3 and it works fine. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1506 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADJ3SPCQQ6LCICMKBRYRQ3UNZK7LANCNFSM5IMTGFMQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[skmcgrail]

I have a root cause for this and have a fix that should make it into our next release. We appreciate this bug report, as this issue impacted a few other service clients. Additionally the root cause also uncovered another situation where idempotency token auto-fill behavior was not configured for some service clients.

[skmcgrail]

The missing SigV4 signing middleware is missing due to a modeling issue that we will work with the service team to get corrected. Until then I have put in a customization that will ensure that the signing middleware is attached to fix that issue.

It looks like that issue in particular is limited to just 6 of the service's operations.

[jaanauati]

@skmcgrail thank you!, regarding the signature issues please see #1500.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[skmcgrail]

Holding this issue open until our next tagged release, but the fix is now merged into main.

[skmcgrail]

Closing this issue, as the changes have been released. You can now go get github.com/aws/aws-sdk-go-v2/service/[email protected] to resolve this issue.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.