feat(aws): support IAM signing for S3 Express - #841
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
S3 Express uses CreateSession credentials and the S3 session-token representation by default. CopyObject, HeadBucket, and UploadPartCopy instead require IAM credentials while retaining the s3express SigV4 signing name. Reqsign already distinguished the header forms internally, but external callers could not select the IAM mode and presigning did not model both token representations.
This exposes a request-signer opt-in for the standard AWS session-token representation across header and query authentication. The default CreateSession representation remains unchanged, and the selection does not modify or replace the caller's Credential.
Deterministic protocol coverage checks exact canonical requests and signatures against the AWS SigV4 implementation and preserves redaction. Live AWS acceptance remains unrun because the gated directory-bucket environment is not configured locally.
Fixes #836