Allow AWS_ENDPOINT_URL_<SERVICE>

[1oglop1]

Describe the feature

Since there is already a support for AWS_ENDPOINT_URL #1193, I think the sdk should support all AWS_ENDPOINT_URL_<SERVICE> and other typical env vars.

https://docs.aws.amazon.com/cli/v1/userguide/cli-configure-envvars.html#envvars-list-AWS_ENDPOINT_URL_SERVICE

Use Case

I run local dynamo DB from the amazon container but emulate other services with the localstack.

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

A note for the community

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue, please leave a comment

[aajtodd]

The SDK does support AWS_ENDPOINT_URL_<service>, can you provide an actual reproduction of something not working?

[1oglop1]

@aajtodd could you point me to the code that's responsible for this, it may be entirely possible I am a few versions behind because it is really difficult to keep the multiple versions in sync. I wish the entire SDK could have a single version to follow similarly to JS or Python.

I have these versions in a lockfile

name = "aws-config"
version = "1.1.9"
name = "aws-credential-types"
version = "1.1.8"
name = "aws-lc-rs"
version = "1.10.0"
name = "aws-lc-sys"
version = "0.22.0"
name = "aws-runtime"
version = "1.1.8"
name = "aws-sdk-cognitoidentityprovider"
version = "1.21.0"
name = "aws-sdk-dynamodb"
version = "1.20.0"
name = "aws-sdk-s3"
version = "1.21.0"
name = "aws-sdk-sqs"
version = "1.18.0"
name = "aws-sdk-ssm"
version = "1.20.0"
name = "aws-sdk-sso"
version = "1.18.0"
name = "aws-sdk-ssooidc"
version = "1.18.0"
name = "aws-sdk-sts"
version = "1.18.0"
name = "aws-sigv4"
version = "1.2.0"
name = "aws-smithy-async"
version = "1.2.1"
name = "aws-smithy-checksums"
version = "0.60.7"
name = "aws-smithy-eventstream"
version = "0.60.4"
name = "aws-smithy-http"
version = "0.60.7"
name = "aws-smithy-json"
version = "0.60.7"
name = "aws-smithy-query"
version = "0.60.7"
name = "aws-smithy-runtime"
version = "1.2.1"
name = "aws-smithy-runtime-api"
version = "1.3.0"
name = "aws-smithy-types"
version = "1.1.8"
name = "aws-smithy-types-convert"
version = "0.60.8"
name = "aws-smithy-xml"
version = "0.60.7"
name = "aws-types"
version = "1.1.8"

but here I found that it should indeed work

aws-sdk-rust/sdk/aws-config/test-data/profile-provider/assume_role_override_service_env_url/env.json

Line 3 in 68dbb59

"AWS_ENDPOINT_URL_STS": "http://aws.sts-env-override"

In my case

AWS_ENDPOINT_URL_DYNAMODB=http://localhost:5001 # does not work
AWS_ENDPOINT_URL=http://localhost:5001 # works

[1oglop1]

Okay I can confirm that, supports definitely AWS_ENDPOINT_URL_DYNAMODB

name = "aws-config"
version = "1.5.10"

@aajtodd thanks for the help. a bit OT, would you be able to guess what is preventing cargo update from updating AWS packages to the latest version? can it be any of the aws packages listed?

[github-actions]

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.