Example of configuring client with smithy-rs (SigV4 signing, url)? #2994
Replies: 2 comments 2 replies
-
While this was previously handled by middleware, it's currently handled as part of the endpoint/auth scheme/identity resolution process in the new "orchestrator". Sigv4 signing is AWS-specific and will be automatically included for any client generated in "AWS-mode". As for how to do that, we still don't have guides for it as the team is specifically focused on tasks related to a 1.0 release. You may be able to get things working by:
|
Beta Was this translation helpful? Give feedback.
-
I wasn't able to get that work, I remember I hacked the interceptors to make it work, is there an easier way to do this now? |
Beta Was this translation helpful? Give feedback.
-
I have a Smithy service generated by smithy-rs behind an API Gateway with IAM authentication. I have generated a smithy Rust client to call this service. I need to add the SigV4 signing to the requests and add the url of the deployed API Gateway endpoint.
I believe this is done by a middleware, but the types were quite confusing and I was not able to make it work. Is there any minimal example for a standard client to use SigV4 signing, as I imagine this is a common usecase.
Beta Was this translation helpful? Give feedback.
All reactions