Access Denied with aws-sdk-java:2.21.6. Worked with aws-sdk-java:2.20.162

[oplohmann]

Describe the bug

Login data is provided with accessKey and secretKey

Expected Behavior

Login should still work as with aws-sdk-java:2.20.162

Current Behavior

Access Denied - although connect worked with aws-sdk-java:2.20.162

Reproduction Steps

Do login using accessKey and secretKey using aws-sdk-java:2.21.6. This should fail. Compare with doing connect same way using aws-sdk-java:2.20.162

Possible Solution

No response

Additional Information/Context

No response

AWS Java SDK version used

aws-sdk-java:2.21.6

JDK version used

JDK 17.0.6 (Amazon.com Inc. 17.0.6+10-LTS)

Operating System and version

Windows 10

[bhoradc]

Hi @oplohmann,

Thank you for reporting the issue. Unfortunately, I am unable to reproduce it. Below is the code sample that I used (aws-sdk-java:2.21.6)

public class Sample {

    public static void main(String[] args) {

        AwsCredentialsProvider creds = StaticCredentialsProvider.create(AwsBasicCredentials.create("accessKeyId", "secretAcessKey"));

        Region region = Region.US_EAST_1;
        ConnectClient connectClient = ConnectClient.builder()
                .credentialsProvider(creds)
                .region(region)
                .build();

        listAllInstances(connectClient);
    }
    public static void listAllInstances(ConnectClient connectClient) {
        try {
            ListInstancesRequest instancesRequest = ListInstancesRequest.builder()
                    .maxResults(10)
                    .build() ;

            ListInstancesResponse response = connectClient.listInstances(instancesRequest);
            List<InstanceSummary> instances = response.instanceSummaryList();
            for (InstanceSummary instance: instances) {
                System.out.println("The ARN  of the instance is "+instance.arn());
            }

        } catch (ConnectException e) {
            System.out.println(e.getLocalizedMessage());
            System.exit(1);
        }
    }
}

Can you please provide the code snippet, using which I can reproduce the issue? And also kindly share the full stacktrace of the error you are receiving.

Thank you.

Regards,
Chaitanya

[oplohmann]

Oh no, I made a blunder ... There is no bug. Hence closed the ticket. Sorry for the trouble caused.

The exception is an Access Denied Error, because my logging does not have write permissions for that bucket being written to. In a testcase I write to a simulated bucket to fill up the simulated bucket with test data. The settings were not set to use the simulated bucket when I upgraded from aws-sdk-java:2.20.162 to aws-sdk-java:2.21.6 and then ran our test casess to see whether things still work after the upgrade.

Reading from the real bucket works with the upgraded version aws-sdk-java:2.21.6.

Just having upgraded to aws-sdk-java:2.21.6 seeing an exception I thought it must have been caused by the upgrade to aws-sdk-java:2.21.6 and didn't even have a look at the exception message. My bad ...

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

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.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[oplohmann]

Oh no, I made a blunder ... There is no bug. Hence closed the ticket. Sorry for the trouble caused.

The exception is an Access Denied Error, because my logging does not have write permissions for that bucket being written to. In a testcase I write to a simulated bucket to fill up the simulated bucket with test data. The settings were not set to use the simulated bucket when I upgraded from aws-sdk-java:2.20.162 to aws-sdk-java:2.21.6 and then ran our test casess to see whether things still work after the upgrade.

Reading from the real bucket works with the upgraded version aws-sdk-java:2.21.6.

Just having upgraded to aws-sdk-java:2.21.6 seeing an exception I thought it must have been caused by the upgrade to aws-sdk-java:2.21.6 and didn't even have a look at the exception message. My bad ...