BuildRiot
Sign in

AISource: AWS

AWS ends creation of new AgentCore Insights jobs ahead of redesign

AWS ended support for creating new AgentCore Insights jobs on October 16, 2026. Existing recurring jobs stop generating reports on October 31. Developers relying on those reports may need interim failure-analysis arrangements beginning October 31.

AWS logo
Cover: BuildRiot

AWS ended support for creating new Amazon Bedrock AgentCore Insights batch and recurring jobs on October 16, 2026, according to its documentation. Existing recurring jobs will process sessions and generate reports through October 30, 2026, with report generation stopping on October 31, 2026. Sources: AWS

Historical batch results and recurring reports remain accessible, AWS said. The notice covers Insights and does not announce a shutdown of other AgentCore services. Sources: AWS

Insights remains in public preview and analyzes agent failures, user intent and execution summaries. It groups session findings into recurring patterns to help developers prioritize defects. AWS’s one-time-report guide still includes job-creation examples, although new Insights jobs are no longer supported. Sources: AWS

AWS attributed the change to a redesign and said a new experience is coming. AWS has given no replacement launch date or retention period for historical reports. Sources: AWS

What to do

  1. Audit automation that creates Insights jobs and review how it handles unsupported job creation. AWS ended support for creating new jobs on October 16, 2026.
  2. Consider whether workflows that depend on recurring Insights reports need interim failure-analysis arrangements beginning October 31, 2026, when report generation stops.
  3. Verify access to historical batch results and recurring reports, which AWS says remain accessible. Sources: AWS

Why it matters

Developers who depend on recurring Insights reports may need interim failure-analysis arrangements beginning October 31. Historical reports remain accessible, but AWS has not committed to a replacement launch date.

Attribution

Sources

  1. 1AWSAgentCore insights: Triage agent failures with pattern analysis - Amazon Bedrock AgentCore
  2. 2AI Provider IndexAWS pauses new AgentCore Insights jobs ahead of a redesignSource published (UTC)
  3. 3AWSOne-time insights report - Amazon Bedrock AgentCore

Read the original source for full details and context.

Report a problem

Links, dates or what you expected. Do not include passwords or private data.

More on AI

All AI stories

Review · AI

GitHub license compliance: dependency policies, package checks and enforcement

GitHub’s documentation describes a package-check API that checks dependency licenses against repository policy. Agent integration is one possible application. Open Source License Compliance is available for Enterprise Cloud, including data-resident deployments; repository enforcement requires Code Security. Setup requires the dependency graph and enterprise policy/ruleset management access, with policy configured under Policies > License compliance > Default policy. The Enterprise Open-Source License Manager role receives notifications to review exception requests. Package checks accept a purls array at /repos/OWNER/REPO/license-compliance/package-checks. The documentation examples use API version 2026-03-10. Fine-grained tokens need Repository license policy: read permission.

GitHub Docs