{"version":"2.1.228","anchor":"bedrock-requests-go-through-middleware-and-streams-become-re","canonical_anchor":"bedrock-requests-go-through-middleware-and-streams-become-re","heading":"Bedrock requests go through middleware, and streams become real SSE","tier":"notice","area":"Bedrock","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/bedrock-requests-go-through-middleware-and-streams-become-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Bedrock requests go through middleware, and streams become real SSE\n\nThe Bedrock backend was rebuilt so streaming and errors behave like every other provider.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- The rewrite moves the model name into the `\/model\/{id}\/invoke` or `\/model\/{id}\/invoke-with-response-stream` path, lifts `anthropic-beta` header values into the request body, and SigV4-signs the result.\n- Responses whose content type includes `application\/vnd.amazon.eventstream` are converted to `text\/event-stream`.\n- Bedrock exception shapes are emitted as `event: error` frames in the stream rather than thrown as backend-specific errors.\n\n**Evidence**\n\n`application\/vnd.amazon.eventstream`\n\n- Area: Bedrock\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}