Breaking change in client-bedrock-runtime #7040

Thanks for pinning this down to the exact commit and for the clear question, and for carrying the same details into #7041 the next day so there is a full thread to point at.

Short answer: the switch is intentional and NodeHttpHandler is not deprecated. That commit added "eventStreamHttp": ["h2", "http/1.1"] to the Bedrock Runtime service model, and the SDK's codegen picks NodeHttp2Handler as the Node.js default whenever a service lists h2 there. HTTP/1.1 stays available by passing the handler explicitly, which is also what kuhe suggested in #7041.

import { BedrockRuntimeClient } from "@aws-sdk/client-bedrock-runtime";
import { NodeHttpHandler } from "@smithy/node-http-handler";

const client = new BedrockRuntimeClient({ requestHandler: new NodeHttpHandler() });

Checked with @aws-sdk/client-bedrock-runtime@3.1134.0 on Node 22.22.1, printing client.config.requestHandler:

default         → NodeHttp2Handler | handlerProtocol: h2
NodeHttpHandler → NodeHttpHandler | handlerProtocol: http/1.1