S3 Blob Store - Timeout waiting for connection from pool

> com.amazonaws.SdkClientException: Unable to execute HTTP request: Timeout waiting for connection from pool
> 	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1207)
> 	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1153)
> 	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:802)
> 	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:770)
> 	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:744)
> 	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:704)
> 	at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:686)
> 	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:550)
> 	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:530)
> 	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5062)
> 	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5008)
> 	at com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1338)
> 	at com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1312)
> 	at com.amazonaws.services.s3.AmazonS3Client.doesObjectExist(AmazonS3Client.java:1393)
> 	at org.sonatype.nexus.blobstore.s3.internal.S3PropertiesFile.exists(S3PropertiesFile.java:76)
> 	at org.sonatype.nexus.blobstore.s3.internal.S3BlobAttributes.load(S3BlobAttributes.java:44)
> 	at org.sonatype.nexus.blobstore.s3.internal.S3BlobStore.refreshBlob(S3BlobStore.java:392)
> 	at org.sonatype.nexus.blobstore.s3.internal.S3BlobStore.get(S3BlobStore.java:379)

Since upgrading to version 3.29 it appears the S3 client is running out of connections to the Blob Store. We are able to redeploy our Docker container for Nexus but then run into the same error again after a while

Hi, We are experiencing similar issues with S3 Blobstore since we upgraded from 3.28.0-01 to 3.29.2-02. We have npm and maven packages repositories backed by this blobstore

From what people say in the last comments of this issue https://issues.sonatype.org/browse/NEXUS-20152, it seems to be the same problem