Consider adding client-config level disable_payload_signing for S3 #1441

Describe the feature

When sending requests over TLS, customers may choose to disable payload signing to avoid the cost of SigV4 signing.

Background

• Added set_payload_override to UploadPartInputBuilder, PutObject, and GetObjectInputBuilder #1087
• rfc to disable payload signing smithy-lang/smithy-rs#3583
• Add operation customization for disabling payload signing smithy-lang/smithy-rs#3915

Since this is an advanced option, it currently only applies to PutObject and UploadPart for S3, and requires per-operation customization:

client
    .put_object()
    // ... other configs
    .customize()
    .disable_payload_signing()
    .send()
    .await;

Ask
Make disable_payload_signing available on the S3 client config builder, so customers don't need to customize each operation call individually.

Notes
For PutObject and UploadPart with a streaming body, calling disable_payload_signing is unnecessary; aws-chunked encoding kicks in by default, which already disables payload signing under the hood.

Use Case

With the request implemented, no per-operation customization needed:

let config = aws_sdk_s3::Config::builder()
    .disable_payload_signing()
    // ... other configs
    .build();

let client = aws_sdk_s3::Client::from_conf(config);

client
    .put_object()
    .bucket("my-bucket")
    .key("my-key")
    .body(body)
    .send()
    .await?;

Proposed Solution

No response

Other Information

No response

Acknowledgements

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

A note for the community

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue, please leave a comment