# Amazon — Architecture patterns for fast session startup on Amazon Bedrock AgentCore runtime

- Company: Amazon (amazon.com)
- Announced: 2026-11-13T22:02:39+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://aws.amazon.com/blogs/machine-learning/architecture-patterns-for-fast-session-startup-on-amazon-bedrock-agentcore-runtime/
- Record: https://forck.live/items/36090-architecture-patterns-for-fast-session-startup-on-amazon-bedrock-agentcore
- Subject: Bedrock / Nova

Amazon's AgentCore runtime now starts agent sessions from a snapshot under platformVersion "V2", preparing the container once instead of for every session. On V1, AgentCore pulled the container image from Amazon Elastic Container Registry, started the container, and ran initialization code before the first request, so cold start grew with image size. V2 starts the container in a fresh microVM, waits for the first healthy ping within 120 seconds, clears the file cache, freezes the microVM, and stores memory and disk as a snapshot. Each create or update now takes a few minutes while the snapshot is built, a change from V1. Restored sessions resume with imports, objects and clients in place, but file reads do not carry over and image files are fetched on first read. AgentCore runtime also now supports build hooks, which the post covers for agents that run separate processes such as a CLI or browser binary.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/architecture-patterns-for-fast-session-startup-on-amazon-bedrock-agentcore-runtime/:

> Agents today review code, process claims, and run unattended for hours. Many also sit behind interactive experiences where a person waits for the first response. Amazon Bedrock AgentCore runtime gives these agents a fully managed, serverless environment: each session runs in its own isolated microVM, the platform scales to zero when there’s no work, and you only pay for the resources your sessions consume.
> 
> AgentCore runtime with platformVersion set to “V2” changes how sessions start. Instead of initializing your container for every session, it prepares your environment once, snapshots it, and restores that snapshot for each new session. Session start times are faster and more consistent. V2 also reclaims memory your sessions don’t use, so your bill tracks what your agent uses.
> 
> For most agents, switching to V2 is all it takes. Some agents need restructuring to get the full benefit, and for chat and voice experiences even 2 seconds is too slow. This post explains how V2 starts a session, how to measure session start time, and how to keep work off the first request, including build hooks, which AgentCore runtime now supports.

---

Record: https://forck.live/items/36090-architecture-patterns-for-fast-session-startup-on-amazon-bedrock-agentcore
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
