AWS shows how AgentCore can deliver the same MCP tools and interactive widgets across compatible AI hosts

High-Frequency AI Prompts for Work, Learning, and Teaching guide

High-Frequency AI Prompts for Work, Learning, and Teaching

Practical AI Side Project Course guide

Practical AI Side Project Course

AWS connects AgentCore evaluations to GitHub Actions for pre-merge agent regression gates

AWS published a reference workflow on September 8 for integrating Amazon Bedrock AgentCore Evaluations with GitHub Actions. The pipeline deploys a development agent and an OAuth-protected MCP server, invokes representative prompts, collects OpenTelemetry traces, and scores behavior before allowing a pull request to proceed. AWS describes built-in dimensions such as helpfulness, correctness, goal success, tool selection, tool parameters, and trajectory order, with custom and code-based evaluators available. The post compares three authentication patterns: evaluating stored traces, using a pre-authorized test user, or issuing machine-to-machine credentials for CI. Its implementation uses the third pattern. Teams should validate that CI credentials cannot escape their intended environment, that evaluation samples cover important failures, and that score variance, latency, evaluator cost, and rollback behavior are visible before treating the threshold as a release gate.

AWS AgentCore Adds Persistent Runtime Instances for Production Agents

AWS announced AgentCore Runtime instances on August 6, 2026. The feature provides persistent, managed EC2 infrastructure for production AI agents, with multi-agent collaboration, GPU support, and sessions lasting up to 14 days. That addresses long-running state and resource continuity, but it does not remove operational responsibility. A safe first trial asks whether a task truly needs hours or days of state, then uses minimal permissions, non-sensitive data, an automatic termination rule, and a cost record covering CPU, GPU, idle time, network access, and session duration. Teams should validate isolation, logging, human approval, backup, and rollback before connecting a persistent runtime to real production data.

AWS Shows AgentCore Policy Workflows with Tenant Isolation and Versioned Skills

AWS’s August 7, 2026 machine-learning case study describes how Cohere Health uses Amazon Bedrock AgentCore to turn clinical prior-authorization policies into structured data. The architecture combines Runtime microVM isolation, Gateway for unified tool access, Memory for session history, and the Agent Skills open standard for versioned domain capabilities. Skills are evaluated with reference data and expert review before release. The reusable lesson is not to automate medical judgment with one prompt. It is to separate tenants, tools, data sources, versions, feedback, and approval, then begin with public or de-identified documents before connecting sensitive business data. Keep the same evidence trail when the workflow changes.

AWS Expands Bedrock AgentCore as Agent Knowledge Retrieval Becomes Managed Infrastructure

AWS announced several Amazon Bedrock AgentCore updates at AWS Summit New York on June 17, 2026. The releases include Managed Knowledge Base, Web Search on AgentCore, AgentCore harness general availability, policy integrations and optimization capabilities, showing that production AI agents are becoming managed infrastructure around knowledge, execution and governance.

A production gate for OpenAI webhooks: signature verification, fast acknowledgement, idempotency, and replay testing

OpenAI webhooks deliver subscribed events as HTTP POST requests to a project-level endpoint. The documentation says the signing secret appears when the endpoint is created and cannot be viewed again, so it must be stored securely for server-side verification. Official SDK helpers can unwrap and verify an event using the raw request body, request headers, and secret. A receiver should return a successful 2xx response within a few seconds and offload non-trivial processing to a background worker. Failed or slow deliveries are retried with exponential backoff for up to 72 hours, while 3xx redirects are treated as failures. Rare duplicate deliveries are possible, so webhook-id should serve as an idempotency key. A release gate should exercise invalid signatures, duplicates, backlog, replay, and recovery before enabling side effects.

Mistral and Cloudera target sovereign enterprise AI with customer-controlled training, inference, and operations

Mistral and Cloudera announced a sovereign enterprise AI partnership on September 10. The companies plan to integrate Mistral models with Cloudera's hybrid data platform across public cloud, private cloud, on-premises, and fully air-gapped environments. Mistral says enterprises will be able to train customized models on proprietary data inside controlled environments while retaining ownership of their data and resulting intelligence. The announcement addresses 30 exabytes of customer-managed data on Cloudera's platform and describes customer control over data, open weights, training, inference, infrastructure, jurisdiction, governance, observability, and the learning loop. It does not identify specific model versions, delivery dates, pricing, certifications, or measured customer outcomes, so buyers still need to translate the sovereignty language into testable contractual and technical controls.

Build interactive MCP Apps using Amazon Bedrock AgentCore