KDCube
← AI Industry News

AgentCore Flips On Per-Agent Telemetry as Bedrock Agents Classic Nears Its Exit

Amazon Bedrock AgentCore now routes new agents' traces to their own CloudWatch log group by default and adds a live ActiveSessionCount metric, just as Bedrock Agents Classic closes to new customers on July 30. It lands two days after the stateless MCP 2026-07-28 spec, which adds a 12-month deprecation ...

Highlights

  • As of today, July 20, 2026, newly created Amazon Bedrock AgentCore runtime agents ship spans to their own CloudWatch log group by default instead of the shared aws/spans pool — per-agent access control, encryption, and export, no code change (AWS).
  • AgentCore now publishes a real-time ActiveSessionCount metric per service type, so operators can alarm on session spikes and watch quota headroom directly (AWS).
  • Amazon Bedrock Agents (the Nov 2023 product) is now "Agents Classic" and closes to new customers on July 30 — two days after the MCP cutover, making late July a real migration window (AWS).
  • The stateless MCP 2026-07-28 spec is 8 days out, and its release candidate adds a formal deprecation policy while retiring Roots, Sampling, and Logging (MCP).

Key Signals

  1. July 2026 release notes AgentCore hardens observability and capacity controls.

    Beyond the July 20 default flip to per-agent span log groups, AgentCore raised default runtime quotas this month to 5,000 concurrent sessions in US East/US West (2,500 elsewhere), 200 interactions/sec, and 25 new sessions/sec per endpoint — and paired them with the new ActiveSessionCount gauge (AWS, AWS). For teams running many agents, telemetry isolation plus live session metrics is the difference between guessing and governing.

  2. aws.amazon.com/bedrock/agents Bedrock Agents Classic sunsets to new customers July 30.

    AWS is steering greenfield work onto the AgentCore runtime and managed harness rather than the 2023-era Agents product (AWS). If you were planning to stand up a new classic Agent, the window shuts this month; existing deployments continue, but the strategic path is now the harness.

  3. MCP release candidate MCP 2026-07-28 gets a deprecation policy — and drops three core features.

    The stateless rewrite graduates Tasks to an extension (anyone on the 2025-11-25 experimental Tasks API must migrate), adds MCP Apps for sandboxed server-rendered UIs, and — critically — sets a minimum 12 months between deprecation and removal going forward (MCP). Roots, Sampling, and Logging are deprecated in this cut. The stability guarantee is the real news for connector maintainers.

Why It Matters / What To Watch

  1. Wire up per-agent telemetry before the default surprises you
    • New agents created today already route spans to their own log group; agents created earlier keep the shared pool unless you set UNIFIED_TRACES_DESTINATION_ENABLED=true — audit which bucket each agent is in (AWS).
    • Add a CloudWatch alarm on ActiveSessionCount now that quotas jumped to 5,000/2,500 — headroom is bigger, but so is the blast radius of a runaway loop (AWS).
  2. Treat late July as a dual migration deadline
    • Inventory any new Bedrock Agents Classic work and re-plan on the AgentCore harness before the July 30 new-customer cutoff (AWS).
    • Port MCP servers/clients to the stateless 2026-07-28 shape and check whether you depend on Roots, Sampling, or Logging — those are now on the clock, even with the 12-month runway (MCP).
  3. Model choice on Bedrock keeps widening
    • OpenAI's GPT-5.6 Sol, Terra, and Luna went GA on Amazon Bedrock on July 9 with a 90% cached-input discount and in-region processing, so the harness's "bring more providers" pitch now includes the newest OpenAI tier alongside Claude and others (AWS).

Quick Links