Updated
Updated · AWS Blog · Nov 9
AWS Makes AgentCore Runtime V2 Generally Available, Holding P75 Cold Starts Near 2 Seconds
Updated
Updated · AWS Blog · Nov 9

AWS Makes AgentCore Runtime V2 Generally Available, Holding P75 Cold Starts Near 2 Seconds

1 articles · Updated · AWS Blog · Nov 9

Summary

  • AgentCore Runtime V2 is now generally available, letting existing Bedrock AgentCore users opt in by setting platformVersion to V2 on new or updated runtimes.
  • P75 cold starts stayed around 2 seconds for container images from 200 MB to 2 GB in AWS tests, versus roughly 5.4 seconds to nearly 30 seconds on the original runtime.
  • V2 also changes memory behavior: sessions start small, page in more on demand, and release memory when idle, which AWS says should cut GB-hour usage and often lower bills despite a higher per-unit rate.
  • Create and update operations take several minutes while snapshots are prepared, and containers must report healthy on /ping within 120 seconds only after initialization completes.
  • The runtime is available in 10 Regions, part of a broader AWS push toward low-disruption upgrades that also includes S3 Tables migration for Hive-to-Iceberg moves and new DynamoDB bulk imports from S3.

Insights

Can Bedrock's snapshotting runtime truly eliminate AI cold starts, or will memory paging introduce hidden latency during complex agent tasks?
Does AWS's seamless migration to managed Iceberg tables secretly trade open-source portability for long-term ecosystem lock-in?
While Lambda's new Kafka queue mode boosts throughput, does sacrificing event ordering secretly shift heavy operational burdens onto developers?