-
Notifications
You must be signed in to change notification settings - Fork 250
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
Added set_payload_override to UploadPartInputBuilder, PutObject, and GetObjectInputBuilder #1087
Comments
agreed we definitely need a way to support this. I think we'll need an RFC / design doc to investigate the best way to support this generally. I think this is probably possible with an interceptor today but definitely not the best user experience. |
I have implemented this by modifying sdk/s3/src/operation/upload_part/builders.rs to add a new function send_with_plugins.
Use case
Is this a good user experience? |
You can now disable payload signing for select S3 operations as of the 12-18-2024 release. |
Comments on closed issues are hard for our team to see. |
Describe the feature
Added set_payload_override to UploadPartInputBuilder, PutObject, and GetObjectInputBuilder to prevent frequent calls to sigv4 when using aws_sigv4::http_request::SignableBody to change object transfers, causing high CPU usage.
Use Case
Proposed Solution
impl UploadPartInputBuilder {
pub fn set_payload_override(mut self, payload_override: ::aws_sigv4::http_request::SignableBody) -> Self {
self.inner.signing_options.payload_override = payload_override;;
self
}
}
Other Information
#1085
Acknowledgements
A note for the community
Community Note
The text was updated successfully, but these errors were encountered: