access-analyzer: upon throttling, AwsServiceException is thrown, instead of ThrottlingException

[OhadR]

Describe the bug

i am using sdk for access-analyzer, 2.33.0
when i hit throttling, i see that i get AwsServiceException , instead of ThrottlingException.
in ThrottlingException there is a method (according to the docs) retryAfterSeconds() so I would like to use it - to know how much time to "sleep". but all i get is AwsServiceException, and when i call isThrottlingException() i get "true".

Regression Issue

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

Expected Behavior

i would expect the SDL to throw ThrottlingException.

Current Behavior

i see that the SDK throws AwsServiceException

Reproduction Steps

call the SDK many times till u hit throttling error.

Possible Solution

No response

Additional Information/Context

No response

AWS Java SDK version used

2.33.0

JDK version used

"21.0.6" 2025-01-21 LTS

Operating System and version

MAC

[debora-ito]

Hi @OhadR

can you share the complete stacktrace, and a minimal sscce repro code if possible?

[bhoradc]

Reproducible code sample:

  public static void main(String[] args) throws InterruptedException {
        AccessAnalyzerClient client = AccessAnalyzerClient.builder().build();
        ExecutorService executor = Executors.newFixedThreadPool(20);
        
        for (int i = 0; i < 100; i++) {
            executor.submit(() -> {
                try {
                    client.listAnalyzers(ListAnalyzersRequest.builder().build());
                } catch (ThrottlingException e) {
                    System.out.println("Message: " + e.getMessage());
                }
                catch (AwsServiceException e) {
                    System.out.println("Error Code: " + e.awsErrorDetails().errorCode());
                    System.out.println("isThrottlingException: " + e.isThrottlingException() + " | " + e.getMessage());
                }
            });
        }
        
        executor.shutdown();
        executor.awaitTermination(30, TimeUnit.SECONDS);
        client.close();
    }

Error Code: TooManyRequestsException
isThrottlingException: true | Too Many Requests (Service: AccessAnalyzer, Status Code: 429, Request ID: 8bceb188-cda3-48d3-9fec-7b7d1e3e0362)

@OhadR - kindly confirm if you meant a different error code in this case instead of TooManyRequestsException .

[OhadR]

thanks @bhoradc , this is a great code sample.
you can see that AWS throws AwsServiceException, rather than ThrottlingException (as expected from the docs.)

Also, as this ThrottlingException doc states, there is a method retryAfterSeconds() that i cannot use if I dont get the ThrottlingException

[bhoradc]

Hi @OhadR

The Access Analyzer service model correctly defines ThrottlingException with a Retry-After header, but in this case my hunch is that it's the API Gateway that could be throttling requests before they even reach the service. This is based on the x-amz-apigw-id header and the TooManyRequestsException error type (which is API Gateway's generic throttling response, not the service-defined ThrottlingException). I will check more on this with the internal service team and get back to you.

Regards,
Chaitanya