Fix bucket exists check to handle 403 errors

[subhashiyer9]

Problem

When the IAM user does not have permissions to ListBucket, it fails with error

software.amazon.awssdk.services.s3.model.S3Exception: Forbidden (Service: S3, Status Code: 403, Request ID: 4N4NV95674Y4J2MF, Extended Request ID: OoAXGw5Yj01ZsVLGY7ag7zvE7BDTFjPEJwoaIWQ4oEKkIa0k5QKEkTXy8TbLnmo4XMes4bKXGIA=)

The existing code for bucket exists was looking for a wrong condition and hence, it was failing with 403 error.

Solution

Fixes the right condition to check for 403 status code

Does this solution apply anywhere else?

• yes
• no

If yes, where?

Test Strategy

Testing done:

• Unit tests
• Integration tests
• System tests
• Manual tests

Release Plan

[confluent-cla-assistant]

🎉 All Contributor License Agreements have been signed. Ready to merge.
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[sonarqube-confluent]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• 0.00% Coverage (0.00% Estimated after merge)
• No duplication information (0.20% Estimated after merge)

Project ID: kafka-connect-storage-cloud

View in SonarQube