Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Expose request compression in the new SDK and coordinate Bedrock support

未关闭
  • 哪里不对？
#110 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

@gouveags 已经在做这个了。

开始于 2026年10月19日。

  • #111 来自 @gouveags —— 未关闭

评估

难度
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 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

aws/aws-sdk-python 的其他 Issue

查看 aws/aws-sdk-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。