-
Notifications
You must be signed in to change notification settings - Fork 196
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
Fully featured SigV4 signer #192
Comments
I think this issue from the botocore repo is relevant. Customers will want the ability to SigV4 sign an arbitrary HTTP request (not just AWS API calls) |
Doesn't our |
not exactly, but it's close. We need examples + an easy path to use our
crate to sign requests going to API gateway
…On Thu, Aug 26, 2021 at 1:10 PM John DiSanti ***@***.***> wrote:
Doesn't our aws-sigv4 crate already provide this functionality?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#192 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADYKZ22XBD24RGZKLRSSJDT6ZYPHANCNFSM4XM7FM6Q>
.
|
not sure if this is the place to ask this, but should the sigv4 support include verification? it'd be nice to use to build services that could use it for their auth |
Opened #1792 with clearer action items to replace this issue. |
Almost certainly via CRT bindings
The text was updated successfully, but these errors were encountered: