The Apache HTTP implementation supports proxy configuration, but Netty does not. This feature should be added to Netty.
Any status updates on this?
@dagnir - any update on this?
Hi @favetelinguis @vinayys we still have this planned, but have not begun work on this yet.
this is very much needed for anyone working in enterprise,.,.,,,,
This is a major issue for us adopting it.
We want to use Spring Boot Webflux to build reactive services. Currently will have to wrap SDK calls in their own separate thread pools rather than just using Netty all the way through.
Spring Boot lets you inject a Reactor Netty HttpClient, but I assume you all are using Netty directly instead of Reactor Netty so that wouldn't be available.
+1
Can we please add the proxy config support for _DynamoDbAsyncClient_ ?????
I am in urgent need.
Hi @BhargavChoksi, this feature was built into the Netty HTTP client instead of at the service clients level. To use the Netty client's proxying feature with the DynamoDB client, you will need to configure the Netty client directly on the client:
SdkAsyncHttpClient.Builder nettyBuilder = NettyNioAsyncHttpClient.builder()
.proxyConfiguration(ProxyConfiguration.builder()
...
.build());
DynamoDbAsyncClient ddb = DynamoDbAsyncClient.builder()
.httpClientBuilder(nettyBuilder)
.build();
Thanks a lot @dagnir, for your quick response. Here, I am able to set proxy-host and proxy-port.
How can I set proxy username and proxy-password?
It seems there is no way to set proxy-username ans proxy-password or I am horribly missing something?
final ProxyConfiguration proxyConfiguration =
ProxyConfiguration.builder().host("http-se.some.host.com").port(8080).build();
Hey @BhargavChoksi That is not currently supported at the moment. This is being tracked here: https://github.com/aws/aws-sdk-java-v2/issues/1432
Marking this is done. Other proxy related features will be tracked separately (e.g. #1432)
Thanks for implementing this, it's working well for me.
One note though, the example configuration here shows using the KinesisClientUtil.createKinesisAsyncClient method which will override setting httpClientBuilder on the KinesisAsyncClientBuilder. Using the KinesisAsyncClient.builder() directly solves this issue.
Most helpful comment
This is a major issue for us adopting it.