What replaces GetEndPointForService?

[epitka-sg]

I am getting warning

'RegionEndpoint.GetEndpointForService(string)' is obsolete: 'This operation is obsoleted because as of version 3.7.100 endpoint is resolved using a newer system that uses request level parameters to resolve the endpoint.'

I am unable to find how it needs to be changed. Any guidance?

Code in question

 healthCheckBuilder
                .AddTcpHealthCheck(options => options.AddHost(Amazon.RegionEndpoint.USEast1.GetEndpointForService("s3").Hostname, 443), "network")

[ashovlin]

With the 3.7.100 release we introduced a new internal mechanism to resolve endpoints across AWS SDKs.

As AWS services grow the endpoint determination logic for some operations is becoming more complicated, and relying on additional information from the request beyond just the client configuration and region pair.

We're internally exploring how to provide a new method that can resolve an endpoint that does support this additional context, and can update this discussion if and when we come up with something.

[muhammad-othman]

DetermineServiceOperationEndpoint method was added to all the service clients as part of v.3.7.624.0, this can be used to know the endpoint that request will use instead of GetEndpointForService.

For example:

            var endpoint = s3Client.DetermineServiceOperationEndpoint(new GetObjectRequest { 
                BucketName = bucketName 
            });

            var url = endpoint.URL;

[jdtsillas]

Is there a more comprehensive example for how to use this new API?
Something which includes creating the client for a given region and service.
With the older API it was straightforward on how to get the RegionEndpoint
for a service and region without having to create a client. One could then
create the client from the RegionEndpoint URL. WIth the new API it seems
that we already need the client to get the endpoint. And we also need a
request? What would that request typically be if we are initializing a session.

[muhammad-othman]

Hi @jdtsillas,

Regions can be selected in the shared config or an environment variable, more details can be found here.
If you want to set it in the code you can do that by passing it to the client constructor, ex: var s3Client = new AmazonS3Client(RegionEndpoint.EUWest3);.
Currently you don't need a RegionEndpoint URL to create a client, since it has the logic to decide the best endpoint to use.
I agree with you the the old API was more straightforward but unfortunately the request is crucial with the new logic, as the endpoint URL might change depending on the request, here is example where the BucketName was used as part of the endpoint URL:

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.