We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS_IGNORE_CONFIGURED_ENDPOINT_URLS and ignore_configured_endpoint_urls are used to disable endpoint urls via environment and shared profile config.
AWS_IGNORE_CONFIGURED_ENDPOINT_URLS
ignore_configured_endpoint_urls
We seem to respect them for the global config when using config loader but not for service specific env/keys (example)
Service specific environment should also take these settings into account when loading from SdkConfig.
SdkConfig
Service clients still use environment settings.
let aws_config = aws_config::defaults(aws_config::BehaviorVersion::latest()).load().await; let sts = aws_sdk_sts::Client::new(&aws_config); let result = sts.get_caller_identity().send().await; println!("resolved ident: {:#?}", result);
export AWS_ENDPOINT_URL_STS=http://127.0.0.1:4566 export AWS_IGNORE_CONFIGURED_ENDPOINT_URLS=true export AWS_PROFILE=my-profile RUST_LOG=trace cargo run
No response
`aws-config: 1.5.6` and latest service clients (sts `1.43.0` at this time).
all
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
AWS_IGNORE_CONFIGURED_ENDPOINT_URLS
andignore_configured_endpoint_urls
are used to disable endpoint urls via environment and shared profile config.We seem to respect them for the global config when using config loader but not for service specific env/keys (example)
Expected Behavior
Service specific environment should also take these settings into account when loading from
SdkConfig
.Current Behavior
Service clients still use environment settings.
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
Version
Environment details (OS name and version, etc.)
all
Logs
No response
The text was updated successfully, but these errors were encountered: