cd /news/ai-agents/aws-ships-agentcore-runtime-v2-and-t… · home topics ai-agents article
[ARTICLE · art-135895] src=forkast.news ↗ pub= topic=ai-agents verified=true sentiment=· neutral

AWS Ships AgentCore Runtime V2 — and the Cloud Agent Infrastructure Layer Is Now Complete

AWS released AgentCore Runtime V2 on September 18, 2026, a microVM-based agent runtime that achieves a P75 cold start latency of 1.9 to 2.0 seconds for images from 200MB to 2GB, down from the 5.4 to 30-second cold starts in V1. AWS bills the runtime at $0.1276 per vCPU-hour and $0.0169 per GB-hour for consumption, and the release completes production-grade agent runtimes across AWS, Google's Gemini Enterprise Agent Platform (January 2026), and Microsoft Azure's AI Foundry Agent Service (July–August 2026). The shift moves competition from agent support to memory management efficiency, state restoration speed, and cost-control granularity.

by read3 min views1 publishedSep 21, 2026
AWS Ships AgentCore Runtime V2 — and the Cloud Agent Infrastructure Layer Is Now Complete
Image: Forkast (auto-discovered)

The Infrastructure Layer Reaches Maturity #

The release of AWS AgentCore Runtime V2 on September 18, 2026, establishes a standardized foundation for cloud-based agents. For builders and enterprise architects, the period of experimental agent environments has concluded, giving way to production-grade infrastructure across the major cloud providers.

AWS, Google, and Microsoft Azure now provide production-ready agent runtimes supported by service level agreements. Google reached this milestone with its Gemini Enterprise Agent Platform (formerly Vertex AI Agent Builder) in January 2026, while Azure completed the rollout of its AI Foundry Agent Service between July and August 2026. Hosting, isolating, and scaling autonomous agents has transitioned from a specialized differentiator to a baseline cloud commodity.

Standardization of the Runtime #

The V2 architecture reflects an industry-wide convergence on microVM-based, isolated, and elastic runtimes. By shifting away from generic container orchestration toward specialized agent environments, cloud providers are addressing the specific requirements of long-running, stateful, and autonomous processes. This evolution is necessary for enterprise-scale deployment, where reliability and hardware-enforced session isolation are non-negotiable.

AWS has addressed previous friction points by introducing elastic memory management, which reclaims unused memory throughout a session. This allows enterprises to pay for actual usage rather than peak allocation. As detailed in the AWS Machine Learning Blog, this architecture achieves a P75 cold start latency of 1.9 to 2.0 seconds for images ranging from 200MB to 2GB. This performance decouples image size from startup speed, a marked improvement over the 5.4 to 30-second cold starts observed in V1.

The New Competitive Frontier #

With the infrastructure layer stabilized, the competitive focus has moved toward runtime architecture. The question of which provider offers agent support is now secondary to the efficiency of memory management, the speed of state restoration, and the granularity of cost control. These factors now determine the viability of an agent platform.

This trend mirrors developments in security and infrastructure, where companies like Cisco, NVIDIA, WSO2, and CrowdStrike embed policy and security directly into the execution environment. As agents gain autonomy, the runtime must serve as the primary enforcement point for identity, security, and resource governance.

Implications for Builders #

For infrastructure engineers, evaluation criteria for agent platforms have evolved to prioritize operational overhead and cost-efficiency. Features like V2’s scale-to-zero capability and consumption-based pricing are central to this. According to AWS, the runtime is billed at $0.1276 per vCPU-hour and $0.0169 per GB-hour for consumption. While the rate for V2 may be higher than previous iterations, AWS notes that the reduction in footprint often leads to a lower total bill for most agents because they consume fewer GB-hours. The runtime environment dictates the capabilities, reliability, and cost-profile of the agent. Whether an agent is processing claims, reviewing code, or coordinating across complex systems, its performance is tethered to the underlying architecture. Future development will focus on persistent compute, such as the EC2-based persistent compute options mentioned in the AWS News Blog, which support long-duration sessions and GPU acceleration.

What Changes for the Industry #

The completion of the infrastructure layer marks the end of the debate regarding which cloud provider supports agents. The industry has moved past the experimental phase, and the focus is now on the architectural nuances of the runtime. For investors and architects, value is found in the efficiency and security of the runtime that powers the agent. As the industry looks toward future developments — including suspend/resume functionality with memory snapshotting and scoped identity for unattended agents — the runtime will remain the primary battleground for enterprise-grade agent deployment.

── more in #ai-agents 4 stories · sorted by recency
── more on @aws 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/aws-ships-agentcore-…] indexed:0 read:3min 2026-09-21 ·