AWS AgentCore Code Interpreter

https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-tool.html

Amazon Bedrock AgentCore Code Interpreter is a managed sandbox service that lets AI agents write and execute code in isolated environments. Each session runs in a dedicated Firecracker microVM with its own CPU, memory, and filesystem, pre-configured with Python and Node.js runtimes and a broad set of data-analysis libraries. Developers and agent frameworks invoke the service via the AWS console, CLI, or the official Python and TypeScript SDKs to run multi-step data analysis and visualization.

Pricing model Per-second, billed on active CPU and peak memory (1-second minimum, 128MB min memory)
Pricing The headline compute price as the provider states it. Sorting ranks prices stated per vCPU over time, converted to hourly. Other pricing models sort after, unranked. $0.0895/vCPU-hour + $0.00945/GB-hour
Free while idle Whether a stopped, paused, or sleeping sandbox costs nothing.
Elastic Resources flex with what the sandbox actually uses, and the bill follows: yes when the provider bills on active or observed use, no when capacity is reserved or allocated and billed while it runs.
Memory snapshots Whether RAM state survives a pause and resume, not just disk.
Wake on request Whether a stopped sandbox wakes automatically on inbound traffic.
Start / resume Typical time from create or resume to running. Sorting ranks stated times, converted to seconds; claims with no figure sort after, unranked. 300-800 ms
Max runtime The longest a sandbox may run. 8 hours (configurable; 15 min default timeout, up to 8h max)
Isolation The isolation technology between sandboxes. Firecracker microVM (per-session, running on AWS Lambda MicroVMs)
GPUs Whether GPU instances are available for sandboxes.
Docker Whether Docker containers can run inside the sandbox.
SDKs Python, TypeScript

✓ yes · ✕ no · – no cited public fact.

Default session timeout is 15 minutes; sessions auto-terminate with data cleanup when it expires, so callers must invoke stop() to release resources promptly.

Sources

Last verified 2026-07-30. Corrections land through the update log.