lcmgh

Issue was on my IAM policies side. I can also confirm it works :) Thanks!

Is this something still being planned by the maintainers? Would love to use the same load testing tool for REST and gRPC.

For reference, this is how I created proxied connections with the latest sdk. ```rust async fn main() { /// .... let shared_config = config_loader(credentials_provider, region, &profile.profile, proxy) .load() .await; aws_sdk_iam::Client::new(&shared_config);...

> Since I just stumbled over that Problem and the snippet from @lcmgh seems to mostly work, just a question, where does the `HyperClientBuilder` come from? `use aws_smithy_runtime::client::http::hyper_014::HyperClientBuilder;` :) Dependency...

I have no working solution for the latest v1 versions of the SDK. https://github.com/tafia/hyper-proxy is also not maintained anymore so it does not support hyper v1.

this gives some hope https://github.com/seanmonstar/reqwest/issues/2107 but no timeline. would be nice if aws could sponsor the development of such things..

Somebody aware of any workarounds?

I found there is `hyper_proxy2` (see https://github.com/hyperium/hyper/issues/3571#issuecomment-1952085625) ```rust use hyper_proxy2::{Intercept, Proxy, ProxyConnector}; use url::Url; use headers::Authorization; use hyper::{Uri}; use hyper_util::client::legacy::connect::HttpConnector; /// Returns `ProxyConnector` if env. variable 'https_proxy' is set pub...

Here is a solution that works with AWS SDK v1. hyper 0.14 can still be used in there (I assumed one has to use hyper v1). https://github.com/awslabs/aws-sdk-rust/issues/1066#issuecomment-1954073162

> We could set it to LevelFilter::Info or even LevelFilter::Off as it is in log. I second `LevelFilter::Off ` as it aligns with behavior known from `log` and makes one...