Agent Sandboxesagentsandboxes.org
Head-to-head

AWS Bedrock AgentCore vs Azure Container Apps dynamic sessions

Answer in brief

Choose AWS Bedrock AgentCore for teams already on AWS that need IAM- and VPC-integrated code execution for agents; choose Azure Container Apps dynamic sessions for Azure-native apps running LLM-generated Python or Node code with egress off by default. AWS Bedrock AgentCore uses MicroVM (Runtime) isolation; Azure Container Apps dynamic sessions uses Hyper-V VM isolation.

By the Agent Sandboxes editors · Updated

Key differences between AWS Bedrock AgentCore and Azure Container Apps dynamic sessions

  • Isolation: AWS Bedrock AgentCore uses MicroVM (Runtime); Azure Container Apps dynamic sessions uses Hyper-V VM.
  • Session length: Up to 8 h (AWS Bedrock AgentCore) versus 220 s / exec (Azure Container Apps dynamic sessions).
  • SDKs and interfaces: Only AWS Bedrock AgentCore lists Python (AgentCore SDK), AWS SDKs and AWS CLI. Only Azure Container Apps dynamic sessions lists REST API, Azure CLI, LangChain, LlamaIndex and Semantic Kernel.

What they have in common

  • Both companies are based in the United States.
  • Both are cloud or model provider services.
  • Neither is open source.

AWS Bedrock AgentCore vs Azure Container Apps dynamic sessions at a glance

AttributeAWS Bedrock AgentCoreAzure Container Apps dynamic sessions
What it isAWS’s managed agent platform: a Code Interpreter tool for running agent-generated code and a Runtime that hosts each agent session in its own microVM.Azure service that hands out Hyper-V-isolated sessions from prewarmed pools, either as a built-in code interpreter or running your own container image.
TypeCloud or model provider serviceCloud or model provider service
IsolationRuntime: a dedicated microVM per user session with isolated CPU, memory and filesystem, sanitized after the session. Code Interpreter: documented as a containerized environment within AgentCoreHyper-V isolation; each session is isolated by a Hyper-V boundary
Open sourceNoNo
Self-host / BYOCNo / Not documentedNo / No
SDKsPython (AgentCore SDK), AWS SDKs, AWS CLIREST API, Azure CLI, LangChain, LlamaIndex, Semantic Kernel
Cold start (vendor claim)No numeric claim; Runtime v2 restores from snapshots for consistent cold startsPrewarmed pools allocate sessions in milliseconds (no specific figure)
Max sessionCode Interpreter: 15 min default, up to 8 hours. Runtime microVMs: up to 8 hours, stop after 15 min idleCode interpreter: 220 s per execution; sessions deleted after a 5–60 min idle cooldown
PersistenceState persists between executions within a session; Runtime can persist filesystem across stop/resume (managed session storage in preview). Large files via S3Session reuse by identifier; files in /mnt/data for the session’s life. Snapshots are not documented; sessions are ephemeral
Snapshots / pauseNot documented / Not documentedNot documented / Not documented
GPUNot documented for Code Interpreter or Runtime microVMs; the separate Runtime “Instances” compute type is described for agents that need GPUsNot documented
NetworkingCode Interpreter network modes: Sandbox (isolated) or Public; VPC connectivity supportedPer-pool egress setting; egress disabled by default
PricingCode Interpreter: $0.0895 per vCPU-hour + $0.00945 per GB-hour, billed per second; CPU billed on actual consumption (not during I/O wait), memory on peakCode interpreter: $0.03 per session-hour (East US, Azure Retail Prices API), billed in one-hour increments. Custom container sessions billed on the Dedicated plan
Free tierNo product-specific free tier is listed; general AWS new-customer credits applyNone stated for dynamic sessions
ComplianceHIPAA eligible and pursuing FedRAMP per the AWS FAQ; AWS reports an internal assessment against programmes including ISO, PCI and SOC, with third-party audits in upcoming cyclesNot documented
Regions15 AWS Regions across North America, South America, Europe and Asia Pacific38 Azure regions listed in the docs
Company headquartersSeattle, Washington, United StatesRedmond, Washington, United States
Good fit forTeams already on AWS that need IAM- and VPC-integrated code execution for agentsAzure-native apps running LLM-generated Python or Node code with egress off by default

Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose AWS Bedrock AgentCore

  • You are already on AWS and want IAM, VPC and CloudTrail integration
  • You need long-running sessions (up to 8 hours)
  • You want consumption-based CPU billing that skips I/O wait

Reasons to choose Azure Container Apps dynamic sessions

  • You build on Azure and want Hyper-V isolation without managing infrastructure
  • You want egress disabled by default
  • You use LangChain, LlamaIndex or Semantic Kernel

Trade-offs to check first

  • AWS Bedrock AgentCore: AWS-only; no self-hosting or other clouds
  • AWS Bedrock AgentCore: Code Interpreter isolation is documented only as “containerized”
  • Azure Container Apps dynamic sessions: 220-second execution limit on the code interpreter
  • Azure Container Apps dynamic sessions: Code interpreter sessions are billed in one-hour increments

Both are worth piloting with your own image and region. See the full AWS Bedrock AgentCore profile and Azure Container Apps dynamic sessions profile, or the complete comparison.

More comparisons

Frequently asked questions

Is AWS Bedrock AgentCore or Azure Container Apps dynamic sessions better for AI agents?
Neither is better for every workload. AWS Bedrock AgentCore suits teams already on AWS that need IAM- and VPC-integrated code execution for agents. Azure Container Apps dynamic sessions suits Azure-native apps running LLM-generated Python or Node code with egress off by default.
What is the difference between AWS Bedrock AgentCore and Azure Container Apps dynamic sessions?
AWS Bedrock AgentCore uses MicroVM (Runtime); Azure Container Apps dynamic sessions uses Hyper-V VM. Session length: Up to 8 h (AWS Bedrock AgentCore) versus 220 s / exec (Azure Container Apps dynamic sessions). Only AWS Bedrock AgentCore lists Python (AgentCore SDK), AWS SDKs and AWS CLI. Only Azure Container Apps dynamic sessions lists REST API, Azure CLI, LangChain, LlamaIndex and Semantic Kernel.
Which is open source, AWS Bedrock AgentCore or Azure Container Apps dynamic sessions?
Neither is open source.
How do AWS Bedrock AgentCore and Azure Container Apps dynamic sessions isolate code?
AWS Bedrock AgentCore: Runtime: a dedicated microVM per user session with isolated CPU, memory and filesystem, sanitized after the session. Code Interpreter: documented as a containerized environment within AgentCore. Azure Container Apps dynamic sessions: Hyper-V isolation; each session is isolated by a Hyper-V boundary.
How does AWS Bedrock AgentCore pricing compare with Azure Container Apps dynamic sessions?
AWS Bedrock AgentCore: Code Interpreter: $0.0895 per vCPU-hour + $0.00945 per GB-hour, billed per second; CPU billed on actual consumption (not during I/O wait), memory on peak. Azure Container Apps dynamic sessions: Code interpreter: $0.03 per session-hour (East US, Azure Retail Prices API), billed in one-hour increments. Custom container sessions billed on the Dedicated plan. Rates change, so check the AWS Bedrock AgentCore and Azure Container Apps dynamic sessions pricing pages before deciding.
Can you self-host AWS Bedrock AgentCore or Azure Container Apps dynamic sessions?
Neither documents a self-hosted option.
How long can sessions run on AWS Bedrock AgentCore and Azure Container Apps dynamic sessions?
AWS Bedrock AgentCore: Code Interpreter: 15 min default, up to 8 hours. Runtime microVMs: up to 8 hours, stop after 15 min idle. Azure Container Apps dynamic sessions: Code interpreter: 220 s per execution; sessions deleted after a 5–60 min idle cooldown.

Sources

  1. docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-tool.html
  2. docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-resource-session-management.html
  3. docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-how-it-works.html
  4. aws.amazon.com/bedrock/agentcore/pricing/
  5. learn.microsoft.com/en-us/azure/container-apps/sessions
  6. learn.microsoft.com/en-us/azure/container-apps/sessions-code-interpreter
  7. learn.microsoft.com/en-us/azure/container-apps/session-pool
  8. azure.microsoft.com/en-us/pricing/details/container-apps/

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

Agent Sandboxes. (2026). AWS Bedrock AgentCore vs Azure Container Apps dynamic sessions. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/aws-agentcore-vs-azure-dynamic-sessions/