feat(aws): add SigV4a signing support - #795
Merged
Merged
Conversation
Xuanwo
marked this pull request as ready for review
July 27, 2026 02:33
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.
AWS SigV4 derives signing keys from a single region, so it cannot authenticate one request across multi-region AWS endpoints. SigV4a uses an asymmetric signing key and a signing region set to cover that use case.
This adds a dedicated
reqsign-aws-v4asigner and extracts credential providers plus canonicalization intoreqsign-aws-core, keepingreqsign-aws-v4focused on HMAC SigV4. The facade retains the existingreqsign::awsAPI for compatibility and exposes explicitaws::v4andaws::v4amodules.The implementation supports header signing and query presigning, preserves the exact wire URI, and validates failure atomicity. It is cross-checked against AWS SigV4a key derivation vectors and the official Rust
aws-sigv4implementation.This also makes the Aliyun default-provider unit test hermetic. Its final fallback previously reached the live ECS metadata endpoint during local workspace tests; the test now disables that unrelated provider and asserts that no HTTP request is made.