Update v4 request signer to log AWS4 canonical request if DEBUG level…

[zoewangg]

… is enabled

Motivation and Context

AWS4 canonical request is important for diagnosing SignatureMismatch errors. It's logged in AbstractAws4Signer prior to 2.20.x, but the new signer DefaultV4RequestSigner doesn't log it, which makes troubleshooting a lot harder.

aws-sdk-java-v2/core/auth/src/main/java/software/amazon/awssdk/auth/signer/internal/AbstractAws4Signer.java

Line 266 in 8ee5634

LOG.debug(() -> "AWS4 Canonical Request: " + canonicalRequest);

Modifications

Update v4 request signer to log AWS4 canonical request at DEBUG level

Testing

Added unit tests

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[cenedhryn]

Thanks for fixing this, it's really important for troubleshooting.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud