AWS SDK for JavaScript v3.1167.0 adds cryptographic request signing for Bedrock AgentCore’s Harness MCP connector and expands AI-powered evaluation support in Amazon Connect. The release also adds private certificate authority support for AgentCore Identity, giving developers several useful changes to check in one update.
AWS AI Watch analysis
What happened
AgentCore’s Harness MCP connector can now use AWS Signature Version 4 request signing. AgentCore Identity also supports private certificate authorities for custom OAuth 2.0 credential providers and custom JWT authorisers, opening support for identity providers that rely on private CAs.
In Amazon Connect, AI-powered automated evaluations now support 96 languages for chat. Voice interactions support 57 languages, specifically those with transcription available through post-call conversational analytics. The v3.1167.0 release notes also list changes including Google Cloud connectors for AWS Config and reusable enhanced snapshots for Amazon Managed Service for Apache Flink.
Why it matters
These are practical building blocks rather than a new model announcement: teams can add signed AgentCore tool requests, connect identity flows that use private CAs, and run automated evaluations across more languages. The voice figure is lower than the chat figure because it depends on post-call transcription support, a distinction worth keeping when “96 languages” threatens to take over the headline.
The release notes describe SDK capabilities, not proof of evaluation quality or a guarantee that every language performs equally well. Still, the changes give developers concrete new options to assess in their AWS applications.
Our read
The strongest AI story here is the combination of broader language coverage in Connect and more flexible identity and signing support around AgentCore. If you build on the JavaScript SDK, check the service-specific changes before upgrading; there is more here than a version number and a ceremonial confetti cannon.
What to watch
- Whether AWS adds more languages to voice evaluations as transcription coverage expands.
- How developers configure private CAs for AgentCore Identity in real deployments.
- Which AWS SDK services adopt the new AgentCore signing support next.
Discussion spark: For AI features in customer-support systems, which should AWS prioritise next: broader language coverage, or stronger controls over identity and tool access?
Sources and evidence
- v3.1167.0 (11 November 2026, 20:07 UTC)
not affiliated with or endorsed by Amazon Web Services (AWS)