AWS AI Updates: September 24, 2026

1. Bedrock Knowledge Bases Got Native Salesforce and Zendesk Connectors

AWS. Amazon Bedrock Managed Knowledge Base now ingests Salesforce knowledge articles and Zendesk articles and community posts through first-party connectors, handling crawling, metadata extraction, and incremental sync from supplied instance credentials. Previously this required a custom ingestion pipeline per platform. The practical effect is that support and sales-enablement retrieval stays current without anyone maintaining the sync job. Source

2. AWS Published a Recipe for Running OpenCode Against Open Weight Models on Bedrock

AWS. A new walkthrough pairs OpenCode, the terminal-native open-source coding agent, with open weight models served from Amazon Bedrock, covering multi-model routing so different tasks hit different models. The pitch is pay-per-use coding assistance where prompts and code stay inside the customer’s own AWS account with no inference infrastructure to run. It is a configuration guide rather than a product launch, but it is the first AWS-blessed path for a BYO-agent setup on Bedrock’s open weight catalog. Source

3. A Single Strands Agent Now Orchestrates Rekognition, Transcribe, and Bedrock for Video Q&A

AWS. AWS detailed a conversational video intelligence architecture where one Strands Agents SDK agent decides at runtime which of Amazon Bedrock, Amazon Rekognition, and Amazon Transcribe to call for a given natural-language question about a video. The design avoids the usual precomputed-index approach, trading some latency for the ability to answer questions the pipeline was not built to anticipate. Source

4. HEMA Built an Internal Assistant on AgentCore With No AWS Credentials on the Client

AWS. Dutch retailer HEMA described HAL, an internal developer assistant built on Amazon Bedrock AgentCore that surfaces governed knowledge through MCP inside the tools its teams already use. Authentication is anchored in Microsoft Entra ID rather than distributed AWS credentials, which is the part worth copying: the client never holds an AWS identity. Source