Setting new JSSE provider for Sqs Async Client #4204
Unanswered
skimwpi
asked this question in
Migration from v1 to v2
Replies: 2 comments
-
@skimwpi currently, custom socket factories are only supported in sync clients. We have a feature request to support in the async clients, tracking here: #2896 |
Beta Was this translation helpful? Give feedback.
0 replies
-
@debora-ito thank you for your reply, much appreciated. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi I'm migrating from v1 to v2 and having difficulty understanding how to use BouncyCastle JSSE provider for async SQS client. In v1, we had
As the code above indicates, I'm using sslcontext-kickstarter library (nl.altindag.ssl) to configure an Apache client with BouncyCastle JSSE provider.
In V2, I'm not understanding how to use SdkAsyncHttpClient (Netty or CRT) to recreate the similiar code for Async client. Both AwsCrtAsyncHttpClient (CRT client) and NettyNioAsyncHttpClient (Netty Client) and their respective builders do not have an approach that I can see which would allow me to set the JSSE provider. Is the feature just not supported with SdkAsyncHttpClient or am I missing a concept here? I do see the ability to tweak TLS configurations like timeouts, etc but not to replace JSSE provider.
Versions:
AWS SDK version I'm migrating to is 2.20.103 from 1.11.1034
Beta Was this translation helpful? Give feedback.
All reactions