-
Notifications
You must be signed in to change notification settings - Fork 862
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide AWS{3,4}Signer that takes a HttpRequestMessage #397
Comments
We don't have a better approach now but making a signing code more accessible is something we want to do for these API Gateway cases. |
Aye, that sounds good. I'm merging what is in the aws4signer and the gist
|
This has been added to our feature request list: https://github.com/aws/aws-sdk-net/blob/master/FEATURE_REQUESTS.md |
I'm using AWS Elastic Search Service and requests need to be signed. There is a nuget package which has to implement the signing code but there's bugs in that library. For example if you try to enable gzip compression it doesn't work and you get the error:
https://github.com/bcuff/elasticsearch-net-aws Is gzip compression compatible with v4 signing? |
Any update on when signer would be available as a utility in sdk? |
Just leaving a +1 for having public API for signing HttpClient requests (or anything really) and not having to use internal namespaces for it. My use case is querying an AppSync GraphQL API protected by V4 signing. |
Having the ability to sign requests for AWS services should be considered a high priority for a production AWS SDK! We just ran into a big roadblock here because I decided to use signed API GATEWAY for a project and one of our backend systems is in .NET and well, oof :/ |
The SDK not enabling authenticating IAM against API Gateways is currently being a blocker. |
Or is there some example of how to convert a HttpRequestMessage to an IRequest that the current AWS4Signer uses.
We're calling api-gateway using IAM authorization which requires the execute-api service, and that requires the AWS4Signature that uses HMAC-256. It would be really nice to have some maintained utility that enables one to sign a generic HttpRequestMessage.
I've copied this gist for now, but I am seeing some discrepancies between what is in the aws-sdk-net AWS4Signer.
Is there a better way than the one I am using?
The text was updated successfully, but these errors were encountered: