An AWS Cognito Identity client is bundled but nothing in the build calls it.
A Cognito identity and temporary-credential client is vendored in with no call site anywhere in this build.
What's wrong with this entry?
The build now carries a client for AWS Cognito Identity, covering identity lookup and temporary-credential exchange plus its error shapes. Nothing in the build calls it, so this does not by itself add a way to authenticate.
- Errors include not-authorized (403), resource conflict (409), too many requests (429), invalid identity pool configuration and developer-user-already-registered.
- The existing STS client was reshaped from lazily initialised modules into plain top-level classes with direct exports, which mainly affects bundle load behaviour.
CognitoIdentityClient", "GetCredentialsForIdentityCommand
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