ContentsTap to jump to a section＋
- The effective date is October 16; the documentation notice gives no separate publication date.
- Existing recurring Insights jobs stop producing reports from October 31.
- The notice concerns Insights rather than a shutdown of all AgentCore agents.
A dated change to agent-analysis jobs
Amazon Bedrock AgentCore documentation states that Insights stopped accepting new batch and recurring jobs on October 16, 2026. Existing recurring jobs continue processing sessions and producing reports through October 30, then stop from October 31.
AWS describes a redesign and says a new Insights experience is coming, without a release date. The notice has an effective date but no separate publication date. Friday Works checked it on October 18.
Insights is the affected component
Insights analyzes agent sessions for failure patterns, user intent and execution behavior. The feature is in public preview. Historical batch results and recurring reports remain available.
Friday Works distinguishes the application, session collection and analysis layer. A dependent dashboard can lack fresh reports even while an agent continues serving users. The notice does not announce a shutdown of every AgentCore agent.
Assign owners to the two deadlines
The October 16 cutoff already affects plans requiring new Insights jobs. October 31 affects existing recurring reports. A report-delivery schedule that still runs without new analysis could create false reassurance.
Inventory jobs, recipients, schedules and decisions that depend on each report. A customer-support team relying on a weekend failure review, for example, needs a replacement information path before the cutoff. This is a planning example, not an observed incident.
Validate monitoring during the transition
Friday Works recommends identifying remaining observation sources and testing a harmless failure scenario in an organization-owned environment. Establish who receives signals when an agent lacks data, fails a tool call or abandons work.
Opening a historical dashboard is insufficient. Preserve access controls when reviewing session data, and do not move customer material into an unapproved tool or region merely to replace a report.
Define completion in terms of fresh signals
Before October 31, document reviewed dependencies, informed report consumers, tested observation alternatives and ownership of historical records. If waiting for the redesign, identify the temporary blind spots explicitly.
These are operational recommendations. Friday Works does not predict a replacement launch date or portray the notice as a wider service retirement. Reassess the plan when AWS publishes additional details.
References
Sources used in this guide
We prioritise official guidance and primary technical sources. Visit each source for full context and the latest updates.
- Insights notice — effective 16 October; existing recurring reports end after 30 October 2026; publication date not specified; checked 18 OctoberAWS ↗︎
- AWS Insights UI example — published 23 July 2026; full original interface captured for product commentary on 18 October; resized only, copyright AWS retained; not an open-licence or customer screenshotAmazon Web Services / screenshot capture Friday Works ↗︎
- Original AWS-published Create insights screen; underlying interface © Amazon Web Services; no fabricated interface or new-availability claimAmazon Web Services ↗︎
- Original AWS-published Failure analysis screen; example data, not Friday Works test evidenceAmazon Web Services ↗︎