A full AWS Bedrock management SDK is bundled but no code in the build calls it.
About a hundred Bedrock control-plane commands are vendored in with no call site in this build.
What's wrong with this entry?
The bundle now carries a full Bedrock management client with roughly a hundred commands (guardrails, evaluation jobs, model customization, import and invocation jobs, inference profiles, provisioned throughput, marketplace endpoints and the automated reasoning policy family) plus paginators and schema definitions. This is management API surface, separate from the Bedrock runtime used for inference, and no code in this build calls it.
AmazonBedrockControlPlaneService
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.228
AWS request signing keeps query strings
Both mention bedrock
-
v2.1.228
Bedrock requests go through middleware, and streams become real SSE
Both mention bedrock