Expose request compression in the new SDK and coordinate Bedrock support
維護者通常 3 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- aws, python
- 領域
- backend, cloud, documentation
研究方向
Read the companion implementation in PR #111 and the Smithy Python issue #854 and PR #855 to understand the shared compression contract and generation workflow. Then inspect the generated Bedrock Runtime client, its client-level tests, and integration guidance mentioned in the issue. Done means adopting the released Smithy behavior through the normal dependency and generation workflow, testing the client configuration, and documenting the service capability requirement; Bedrock and Mantle support also needs coordination.
由索引模型根據 Issue 內容生成。
描述
Describe the feature
I'd like the new async Python SDK to expose request-body compression through its generated client configuration, and to establish how Bedrock and Mantle can support it.
We use AWS-hosted models for conversation-heavy agents. As conversations and tool results grow, uploading the next request becomes part of the wait before the first token. Giving applications an explicit compression choice would be a useful product capability for AWS-hosted inference.
Use Case
Anthropic announced gzip in Claude Code, and its changelog documents compression for large requests to api.anthropic.com. OpenAI documents zstd request bodies for the Responses API.
AWS offers models from these providers through Bedrock and its Mantle endpoint. I'd like AWS applications to be able to use supported compression capabilities too, without maintaining custom HTTP transports. Compression can reduce upload time; the benefit depends on payload size and the network. It doesn't reduce model tokens.
In checks on October 18, 2026 in us-east-1, matched requests using Anthropic Haiku succeeded uncompressed through Bedrock Converse/ConverseStream and Mantle Messages, including streaming responses. Gzip and zstd requests returned HTTP 400; Bedrock reported Unable to parse request body. This needs service coordination alongside the SDK implementation.
Proposed Solution
The companion PR adopts Smithy Python's shared compression implementation through the usual generated client configuration. An explicit request_compression_encoding="gzip" choice applies to supported requests without a size threshold, alongside an automatic mode. Unsupported explicit choices and conflicting disable settings fail before sending. The companion implementation supports gzip under the current Smithy contract; zstd needs a coordinated follow-up covering the contract and service support.
The explicit choice makes compression a requirement. A zero automatic threshold would still allow operations without compression metadata to send uncompressed requests; explicit gzip should fail before sending in that case.
The shared runtime and generator changes belong in Smithy Python. This repository should adopt that behavior through its normal generation and dependency workflow, with client-level tests and guidance explaining the service capability requirement. Adoption depends on a Smithy release containing the implementation. We should not manually advertise compression on Bedrock operations that don't accept it.
This generated client covers modeled Bedrock Runtime operations. Mantle's provider-compatible APIs need a separate API/client integration.
The diff includes client tests and guidance for this integration. I'd appreciate feedback on the generation and release process, and help connecting with the Bedrock/Mantle service owners. The checks above cover only the named Haiku routes; they include no OpenAI-route test or latency measurement.
Other Information
Companion implementation: PR.
- Smithy Python: shared runtime and code generation — issue, PR.
- Botocore: explicit compression choice for the existing SDK — issue, PR.
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
Affected area
service client (generated client under clients/), code generation, documentation
Relevant package(s)
aws-sdk-bedrock-runtime; shared compression implementation in smithy-python.
Source reviewed at 8f209d245501792c7b18ce197c194170ca4d6564.
Python version used
Python 3.12.13 for the companion implementation's local tests. See the companion PR for validation details.
- 主要語言
- Python
- 星號
- 176
- 分支
- 25
- 平均合併
- 3 天 3 小時
- 30 天內合併 PR
- 8
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
aws/aws-sdk-python 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
aws/aws-sdk-python#13 ·
維護者通常 3 天內回覆
-
難度 5/5 一週以上 新手友好度 25/100
aws/aws-sdk-python#99 ·
維護者通常 3 天內回覆
-
feature-request p3 queued
難度 5/5 一週以上 新手友好度 35/100
aws/aws-sdk-python#92 ·
維護者通常 3 天內回覆
-
announcement
難度 5/5 一週以上 新手友好度 25/100
aws/aws-sdk-python#90 ·
維護者通常 3 天內回覆
-
announcement
難度 3/5 1-2 天 新手友好度 35/100
aws/aws-sdk-python#84 ·
維護者通常 3 天內回覆
查看 aws/aws-sdk-python 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
-
Status: Triaged Type: Enhancement
難度 1/5 1 小時以內 新手友好度 82/100
canonical/craft-store#448 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
維護者通常 1 天內回覆
-
good first issue research size:s skill:numerics sub-issue
難度 2/5 1-3 小時 新手友好度 78/100
SKaiNET-developers/SKaiNET#1372 ·
維護者通常 1 天內回覆
-
debt
難度 2/5 1-3 小時 新手友好度 68/100
microsoft/vscode-flake8#601 ·
維護者通常 1 天內回覆