Support S3AsyncClient from software.amazon.awssdk:s3

[vlbaluk]

Are you going to put S3AsyncClient implementation alongside synchronous in the near future? We will switch to the S3 Async client, but rewriting tests is blocked.😐

[afranken]

@vlbaluk did you get an AsyncClient to work in your tests? It should be easily possible to do so.
I can look into adding Async versions to the test infrastructure in one of the next releases for convenience.

[vlbaluk]

Hey @afranken, Thank you for asking.

It is not functioning as expected with S3TransferManager, which should enable multipart uploading and downloading by default.

1. File content on the S3 mock Docker container contains not only data but also metadata, which leads to incorrect downloads.
2. S3Mock always returns incorrect length for multipart downloads, too.

Experiment, file content is "BBBBB"

• Async CRT client with multipart and S3TransferManager stores the following file in S3Mock docker container:

• Synchronous client stores correct content:

Code snippet:

store.write("test data".getBytes(UTF_8));
 // under the hood, s3TransferManager.uploadFile(uploadFileRequest) with CRT async client


s3TransferManager.download(downloadFileRequest).completionFuture().join().result().response().contentLength() 
// download returns incorrect content, including additional lines at the beginning and at the end, as on the screen above.