-
Notifications
You must be signed in to change notification settings - Fork 910
Unable to work with Kinesis when behind proxy #685
New issue
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
Comments
Hi @mscharp, sounds like you're using versions
Yes, they're currently only available in the preview releases. They were excluded from
Yes, this is something that we want to support. If you're willing to put a PR together, we'll be happy to take a look 😄 |
Ok great. Thanks for the clarification on the 2.0.1 vs the preview sdks. |
I have the same question - how do i set proxy to KinesisAsyncClient, i am using 2.0.6. |
@rjinoy We have yet to implement this for the Netty HTTP client (our default for all async clients). Feel free to thumbs up the original comment so we can help prioritize this against other pending feature requests 😃 |
Is there a KinesisSyncClient ? |
@rjinoy Yes there is, but at the moment, they're only in the preview versions, not in |
Is there a proxy support for KinesisSyncClient ? |
@rjinoy Unfortunately not. The latest updates in the We don't have an ETA for proxy support in Netty yet, but it's in our backlog. We're also more than happy to take a look at a PR if you'd like to tackle this 😄 |
Sure, this is important for me, without the proxy support i cant use KCL. |
Many AWS customers work behind corporate proxies, so the entire library cannot be leveraged without it |
Hi @dagnir |
Closing in favor of #858 |
…95e06ce5 Pull request: release <- staging/4f667181-cddd-4f0a-b90e-8a1b95e06ce5
I'm attempting to update my "stock-trader" sample application to use the new 2.0 sdk ( in prep for updating a real application ). The only Kinesis Client that I can create is the KinesisAsyncClient, which uses the Netty Http client. This is a problem because the AWS version of the netty-http-client doesn't support proxy configuration.
Will there be a KinesisSyncClient? When will it be available? If not, any reason?
Will proxy config support be added to the Netty Http Client?
I'm not opposed to submitting a PR for adding proxy config support to the netty http client if I can figure it out. Are there any particular reasons why it wasn't added in the first place of which I should be aware?
thanks!
The text was updated successfully, but these errors were encountered: