The Bedrock backend was rebuilt so streaming and errors behave like every other provider.
What's wrong with this entry?
The AWS Bedrock backend was rebuilt. It no longer swaps in a custom stream class; instead it rewrites each outgoing request and translates Bedrock's binary event stream into a standard server-sent-events response, so streaming and errors behave like every other backend.
- The rewrite moves the model name into the
/model/{id}/invokeor/model/{id}/invoke-with-response-streampath, liftsanthropic-betaheader values into the request body, and SigV4-signs the result. - Responses whose content type includes
application/vnd.amazon.eventstreamare converted totext/event-stream. - Bedrock exception shapes are emitted as
event: errorframes in the stream rather than thrown as backend-specific errors.
application/vnd.amazon.eventstream
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Bedrock inference profile lookup failures are logged
Both mention bedrock
-
v2.1.239
AWS credential resolution now sees the configured region
Both mention bedrock
-
v2.1.239
AWS and Google endpoint variables handled explicitly
Both mention bedrock