Kess Plasmeier

Hello Sid22, The Async S3 Encryption Client uses the Java implementation Reactive Streams to send data to S3. This is generally more efficient, but for multipart uploads, there are issues,...

I see, that makes sense then. If you're using the the low-level multipart upload API, then setting `enableMultipartPutObject(true)` won't have any affect, it only modifies the behavior of `putObject`, in...

Hello Ahmar, I was able to reproduce this. The issue here is that when we implemented ranged gets in S3EC v3, we decided to maintain compatibility with the S3EC v1/v2...

Hey there, thanks for submitting this issue. We were able to reproduce this, and it is fixed in the latest release: https://github.com/aws/amazon-s3-encryption-client-java/releases/tag/v3.1.3 Let us know if you have any other...

Upon further investigation, this behavior is due to the implementation of the AWS SDK's `InputStreamSubscriber`. We have filed a bug with the SDK team; once the fix is published, we'll...

Hey Nathan, Could you share what credential provider you're using? This is generally unexpected behavior; the KMS client is instantiated using the `credentialsProvider` that's passed to the S3EC's builder. Based...

Hey @NathanEckert, When you set the `credentialProvider()` on the S3 Encryption Client and supply a KMS key ID, the S3EC will use that credential provider for the S3 clients AND...

Hey @andrewnmiferreira, Thank you for reaching out. What version of the AWS SDK are you using? Could you try upgrading to the recently released S3EC version 3.3.2 and see if...

Hey @tbaeg , Thanks for the bug report. For valid ranged get requests, this behavior is fixed in the recently released version 3.3.3. Please upgrade and let us know if...

Hey @andrewnmiferreira, We identified an issue with the `Subscriber` implementation and have released a fix in version 3.3.5. Can you upgrade to this version and let us know if this...