Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Expose request compression in the new SDK and coordinate Bedrock support

Aperta
  • Qualcosa non va?
#110 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

@gouveags ci sta già lavorando.

Dal 19/10/2026.

  • #111 di @gouveags — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
aws, python
Ambito
backend, cloud, documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
176
Fork
25
Merge medio
3g 3h
PR unite (30g)
8

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aws/aws-sdk-python

Tutte le issue di aws/aws-sdk-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.