Skip to content

Add managed SigV4a signer. #3881

@teo-tsirpanis

Description

@teo-tsirpanis

Describe the feature

Using the AWS SigV4a signature scheme it in the AWS SDK for .NET currently requires an extra NuGet dependency to the native aws-c-auth library. However, all the frameworks supported by V4 have the required elliptic curve cryptography APIs to implement SigV4a entirely in managed code.

Use Case

Eliminate optional dependency to native code and increase platform compatibility.

Proposed Solution

  • AWS4aSigner class gets added.
  • AWS4aSignerCRTWrapper class and all related APIs in AWSSDK.Core and AWSSDK.Extensions.CrtIntegration get deprecated.

Other Information

I have started an implementation on my machine, will open a PR soon.

Acknowledgements

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

AWS .NET SDK and/or Package version used

AWSSDK.Core V4

Targeted .NET Platform

All supported frameworks

Operating System and version

All supported operating systems

Metadata

Metadata

Assignees

Labels

feature-requestA feature should be added or improved.lEffort estimation: largequeued

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions