terrywbrady
commented
4 months ago Open dloy opened 4 months ago
terrywbrady
commented
4 months ago 
martinhaye
commented
4 months ago David added this info in a request to Kurt: "I became aware that AWS is freezing their version 1 of the java S3 sdk in 2025. We use this code for all of our server s3 handling (AWS, SDSC, and Wasabi). There is some complexity in the retry logic that required several failed attempts to get this code working especially with SDSC and Wasabi. Would it be inappropriate to request that our AWS rep. see if the AWS v2 group could provide the equivalent for this block of v1 code I have?"
Let's discuss and get the retry code to IAS, so that we can discuss with Kevin and company.
terrywbrady
commented
4 months ago Discussed at 7/23 IAS meeting
dloy
commented
3 months ago Response SDSC from Gavin Biffar: Hi David,
Sorry for the delay. Qumulo tells me there are no major caveats with the AWS Java SDK v2. The key requirements are to use path-style addressing and enable signature v4 signing.
Thanks, Gavin
dloy
commented
3 months ago From Wasabi: From Denis at Wasabi:
In the interim, please find this KB article on version 2 of the Wasabi sdk:
https://docs.wasabi.com/docs/how-do-i-use-aws-sdk-for-java-v2-with-wasabi?highlight=aws%20s3%20java
and this one too.
https://docs.wasabi.com/docs/aws-1
Kind regards, Denis
Current java S3 support in Merritt uses version 1 AWS SDK. Through most of 2022-23 v2 provided a fraction of the features in v1. This has changed and with the dropped support of 12/31/2025, it is now critical that version 1 be upgraded to version 2. As of July 31, 2024, v1 is maintenance mode only.
The impacts of these changes need to be explored since this underlying code is used in Storage, Audit and Replication. Hopefully(!) the existing API can continue with the underlying code replaced but the details need to be evaluated.