S3 put object to MRAP fails but worked on git rev e03a5aa

[Jacob-Burckhardt]

Describe the bug

Aws::S3::S3Client::PutObject fails with an MRAP.

Regression Issue

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

Expected Behavior

I expected it to say:

Added object 'object.txt' to bucket 'arn:aws:s3::000000000000:accesspoint/aaaaaa.mrap'.

To protect my confidentiality, I changed my real arn to the above arn that used the above zeros and the aaaaaa.

Current Behavior

It says:

Error: putObject: SDK failed to sign the request

Reproduction Steps

The example fails when run with arguments of:

object.txt arn:aws:s3::000000000000:accesspoint/aaaaaa.mrap

Possible Solution

• git rev e03a5aa succeeds.
• Or using a simple bucket name that is not an MRAP makes it succeed with both SDK versions.

Additional Information/Context

No response

AWS CPP SDK version used

1.11.723

Compiler and Version used

Debian clang version 19.1.7 (3+b1)

Operating System and version

Debian 13.2

[sbiscigl]

Or using a simple bucket name that is not an MRAP makes it succeed with both SDK versions.

not following this comment, are you saying it fails on non-mrap buckets too? we run nightly tests with non-mrap buckets that are succeeding on main.

Sorry i see now, you were saying it does work on non mrap

[sbiscigl]

Yeah i verified the error you're seeing. It has to do with this code change that refactored chunked encoding for S3 from the http client implementation themselves up to generic interceptors in the SDK. This was to unblock the use of custom http clients. Looks like what this refactor missed was

If SDKs have SRA based interceptors they MUST use the modify_before_transmit handle for request mutation.

The concept of interceptors can be found here. There was a implementation error in the refactor that moved it to

modifyBeforeSigning - called before the request is signed; this method can modify and return a new request

instead of

modifyBeforeTransmit - called before the transport request message is sent to the service. Which causes the sigva signer to choke on the content encoded body.

This interceptor should occur after signing, having it before signing causes this error. fixing this, treating it as high priority. Sorry about this working on a fix ASAP

[sbiscigl]

should be fixed on main now, will be tagged this afteroon tomorrow with version1.11.725, give it a shot and let me know you have any questions

[Jacob-Burckhardt]

Your new version works. Thanks for the fix!

[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.