@aws-sdk/signature-v4-multi-region

[justin-masse]

Describe the feature

@smithy published a new version of sigv4a spec implementation recently and am curious if this can be updated in @AWS-SDK multi-region signing package in order to remove the need for CRT package for signing which allows us to more easily sign requests in a node lambda runtime without needing to implement some ugly work arounds due to relative pathing to binaries within the aws-crt package.

Use Case

Using sigv4a without need for aws-crt binaries in a node lambda runtime

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

SDK version used

latest

Environment details (OS name and version, etc.)

node 22 on lambda

[kuhe]

@aws-sdk/signature-v4-multi-region does not take a direct dependency on @aws-sdk/signature-v4-crt and the aws-crt.

Rather, it requires that the user load a sigv4a implementation, the only choice of which to this point was @aws-sdk/signature-v4-crt.

With the release of @aws-sdk/signature-v4a, this package can be loaded instead of @aws-sdk/signature-v4-crt. We only recommend this when the CRT is not usable.

https://github.com/aws/aws-sdk-js-v3/tree/main?tab=readme-ov-file#using-javascript-non-crt-implementation-of-sigv4a

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.