High CPU Usage in S3 Java SDK Due to Excessive URL Parsing and Exception Stack Trace Generation During getObject Requests

[jasonstack]

Describe the bug

We are using software.amazon.awssdk:S3:2.29.21: DefaultS3AuthSchemeProvider#resolveAuthScheme seems to parse the String endpoint on every request and catching exceptions when some endpoint rule is mismatched in DefaultS3EndpointProvider#endpointRule64.

This is how we configure the client.

        S3CrtAsyncClient.builder()
                .credentialsProvider(StaticCredentialsProvider.create(AwsBasicCredentials.create(accessKey, secretKey))
                .retryConfiguration(b -> b.numRetries(3))
                .checksumValidationEnabled(true)
                .forcePathStyle(true)
                .endpointOverride(URI.create(endpoint));

Attached CPU profile:

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Avoid parsing URL and filing stacktrace on endpoint rule mismatch per request

Current Behavior

Parsing URL on every request and filling stacktrace when endpoint rule mismatches

Reproduction Steps

Run getObjects request

Possible Solution

No response

Additional Information/Context

No response

AWS Java SDK version used

2.29.21

JDK version used

21

Operating System and version

Ubuntu

[sugmanue]

This is not a bug, but the expected behavior. Granted, we could improve its performance a bit, but the behavior is required for S3 to work correctly.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[sugmanue]

Fixed on #5911

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[jasonstack]

thanks for improving it!

[sugmanue]

Thank you for the through report!

[AlySheeM]

This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.