Smithy-modeled endpoint resolution and AWS config.

[nikpivkin]

Hi! Field EndpointResolverWithOptions is has been declared deprecated in the Config. What is now the way to configure the endpoint for the config? Except for the endpoint configuration for each individual service.

[RanVaknin]

Hi,
Please check out to our documentation and examples for Endpoints2.0
https://aws.github.io/aws-sdk-go-v2/docs/configuring-sdk/endpoints/
Please let me know if this helps.
Ran~
Answer:

[github-actions[bot]]

Hello! A team member has marked the above comment as the likely answer to this discussion thread.

• If you agree, please upvote that comment, or click on Mark as answer. I will automatically mark the comment as the answer next time I check.

• If this answer does not help you, please downvote the answer instead and let us know why it was not helpful. I will add a label to this discussion to gain attention from the team.

[nikpivkin]

Hi @RanVaknin ! Thanks.

But I think you didn't quite understand the question. How do I configure the endpoint for the configuration and not for each individual client?

Below I have given an example of the code:

customResolver := aws.EndpointResolverWithOptionsFunc(func(service, region string, options ...interface{}) (aws.Endpoint, error) {
    if service == s3.ServiceID {
	some code
    }
    return aws.Endpoint{}, fmt.Errorf("unknown endpoint requested")
})

// Loading configuration from ~/.aws/*
cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithEndpointResolverWithOptions(customResolver))
if err != nil {
    log.Fatal(err)
}

s3Client := s3.NewFromConfig(cfg)
// and all the other clients

[nikpivkin]

@RanVaknin Hi! I still haven't solved the problem with migrating to endpoint v2.

[nikpivkin]

We use over 30 clients and cannot configure endpoints for every client.

[nikpivkin]

I realized it was impossible to do that now. It would be nice if there was a mention of this in the documentation, such as in the migration section.

// Deprecated: The global endpoint resolution interface is deprecated. The API
// for endpoint resolution is now unique to each service and is set via the
// EndpointResolverV2 field on service client options. Use of
// WithEndpointResolver or WithEndpointResolverWithOptions will prevent you
// from using any endpoint-related service features released after the
// introduction of EndpointResolverV2. You may also encounter broken or
// unexpected behavior when using the old global interface with services that
// use many endpoint-related customizations such as S3.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.