Close S3 lifecycle leaks of AWS classes

Author: qqmyers

src/main/java/edu/harvard/iq/dataverse/dataaccess/S3AccessIO.java

@@ -1555,4 +1555,16 @@ public static String getNewIdentifier(String driverId) {
         return driverId + DataAccess.SEPARATOR + getConfigParamForDriver(driverId, BUCKET_NAME) + ":"
                 + FileUtil.generateStorageIdentifier();
     }
+
+    public static void closeAll() {
+        logger.info("Closing all S3 clients and transfer managers.");
+        driverTMMap.values().forEach(S3TransferManager::close);
+        driverTMMap.clear();
+        driverClientMap.values().forEach(S3AsyncClient::close);
+        driverClientMap.clear();
+        driverPresignerMap.values().forEach(S3Presigner::close);
+        driverPresignerMap.clear();
+        // AwsCredentialsProvider does not need to be closed unless it's a specific implementation that requires it.
+        driverCredentialsProviderMap.clear();
+    }
 }

src/main/java/edu/harvard/iq/dataverse/dataaccess/S3LifecycleBean.java

@@ -0,0 +1,15 @@
+package edu.harvard.iq.dataverse.dataaccess;
+
+import jakarta.annotation.PreDestroy;
+import jakarta.ejb.Singleton;
+import jakarta.ejb.Startup;
+
+@Singleton
+@Startup
+public class S3LifecycleBean {
+
+    @PreDestroy
+    public void cleanup() {
+        S3AccessIO.closeAll();
+    }
+}