Support endpoint configuration via env and shared config

[adrianlungu]

Describe the feature

Given that the AWS-CLI has received support for endpoint configuration via AWS_ENDPOINT_URL env vars, or the shared config file, as detailed here: https://aws.amazon.com/blogs/developer/new-improved-flexibility-when-configuring-endpoint-urls-with-the-aws-sdks-and-tools/

It would be nice if the Go AWS SDK also supported this to be able to configure the AWS endpoint url automatically as done with other variables, without having to explicitly specify it in code.

Use Case

Configuring the AWS session via environment variables or the shared configuration file without having to maintain the variable in multiple places to pass it to code via a WithEndpoint func.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS Go SDK V2 Module Versions Used

github.com/aws/aws-sdk-go-v2 v1.20.1

Go version used

go1.20.5, MacOS Ventura 13.5

[lucix-aws]

Thanks for the feature request.

This is actually a cross-SDK initiative (and it appears it has already landed in the CLI) that we were tracking internally. We'll leave this feature request open for visibility.

[bhechinger]

I was just searching this exact thing yesterday myself as well. Is there any idea of an ETA for when this might be released?

[lucix-aws]

Will be resolved by #2328.

[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.

[lucix-aws]

This is being held back from release temporarily to investigate/resolve a moduling issue which is preventing us from being able to perform the minimum go version bump to 1.19.

Resolved and re-merged.

[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.