Description
Describe the bug
As said in #3813, I also agree that the S3CrtAsyncClientBuilder
is missing a lot of functions available for S3AsyncClientBuilder
. But for me, the case causes a pretty large bug, since I cannot connect to the implementation of the S3 I use (Ceph), while I could do that with the S3AsyncClientBuilder
using forcePathStyle
.
Expected Behavior
I'd expect the AWS CRT SDK to be able to connect to the S3 implementation I use as usual, but in practice, it fails to do so and I get the error of: software.amazon.awssdk.core.exception.SdkClientException: software.amazon.awssdk.crt.s3.CrtS3RuntimeException: Host name was invalid for dns resolution
. Enabling the forcePathStyle
option would probably make this work.
Current Behavior
I cannot migrate to the CRT implementation even though I really want to since I need the multipart uploading logic and I don't want to implement this all by myself just because I'm not able to connect to S3 using the crt client.
Reproduction Steps
Cannot be provided since this error getting thrown only when I connect to the S3 implementation of Ceph.
Possible Solution
Adding the forcePathStyle
Additional Information/Context
No response
AWS Java SDK version used
2.20.17
JDK version used
17.0.2
Operating System and version
Windows 10