# Amazon Bedrock AgentCore vs E2B

AgentCore is AWS's platform to host and govern agents, with a microVM per session. E2B is a sandbox SDK. They are compared when a team picks where agent code runs.

Facts checked 17 October 2026. Prices and limits move. Read the citations.

Neither product is ours. Rush is, and it gets one paragraph below. Every cell is from the vendor's own pages.

**The short answer.** Pick AgentCore when the agent must live inside AWS with its identity, policy and audit. Pick E2B when you want a sandbox SDK you can self-host anywhere.

## The useful distinction

Amazon Bedrock AgentCore: a modular AWS platform to host, run and govern agents of any framework: a microVM runtime, a managed harness, gateway and MCP, memory, identity, browser, code interpreter, policy and evals.

E2B: Firecracker microVM sandboxes driven from an SDK. Your agent runs code there; the loop, the git steps and the pull request are your code. Rush itself runs on E2B.

## Buyer questions

| Question | Amazon Bedrock AgentCore | E2B |
| --- | --- | --- |
| What runs | Your framework (LangGraph, Strands, CrewAI, OpenAI Agents SDK, Claude Agent SDK), or the managed harness built on Strands Agents. | None built in. You bring the agent; E2B ships a prebuilt claude template and guides for Codex and OpenCode. |
| Isolation | Each user session in a dedicated microVM, up to 8 hours, or 14 days on Instances. Filesystem can persist across stop and resume. Browser and Code Interpreter run in containers, 15 minutes by default. | Firecracker microVMs with dedicated kernels. A paused sandbox keeps its filesystem and memory, with no automatic deletion. |
| Result and pull request | Left to you. Results come back over the API, a stream or a WebSocket; GitHub appears only as an outbound sign-in target. | Left to you. E2B's Claude Code guide clones with your token, runs the agent and reads git diff; pushing and opening the pull request is your code. |
| MCP | Agents use tools over MCP or A2A. Gateway turns APIs and Lambdas into MCP tools and connects existing MCP servers. | An MCP gateway inside the sandbox reaches 200+ servers from Docker's catalog, or servers you run yourself. |
| Team | IAM, AgentCore Identity with Okta, Entra ID or Cognito, a Registry of agents and tools, and a browser Live View a person can take over. | An SDK for your own product. No shared task view or Slack and Linear surface on the pages we read. |
| Starting price | Runtime $0.0895 per vCPU-hour and $0.00945 per GB-hour; up to $200 Free Tier credit for new AWS customers | Hobby $0 with a one-time $100 credit; Pro $150 / month plus usage |
| Where it taps out | 8-hour microVM sessions. The managed harness is Strands-based, not the Claude Code or Codex CLI. No pull request or proof loop: you assemble Runtime, Gateway, Identity and Observability. | Sessions end at 1 hour on Hobby and 24 hours on Pro unless paused. Sandboxes reach the open internet by default. No result or pull request layer. Pro has a $150 monthly fee before usage. |

## When each side wins

### Amazon Bedrock AgentCore wins when

- You need enterprise governance: Cedar-compatible policy, identity from your IdP, CloudTrail, a registry and evaluations.
- Everything must run in your own AWS account and regions, with multi-day Instances and GPUs.
- You want CPU billed down to zero during I/O wait, and browser sessions recorded to S3.

### E2B wins when

- You want raw SDK control over each sandbox, for an agent you wrote or for work that is not an agent at all.
- You must self-host: the runtime is Apache-2.0, runs on one KVM host or ships as Terraform for AWS, GCP and Azure, and E2B also offers BYOC.
- You want published per-second rates for CPU and RAM and up to 1,100 concurrent sandboxes on its top published tier.

## Where Rush sits

Rush runs on E2B and is a finished loop for one job, not a platform: send a task, get the pull request or report back.

## Skip Rush if

- Rush runs three agents: Claude Code, Codex and OpenCode. It does not host an agent you wrote yourself.
- Repositories come through the Rush GitHub App. A GitLab or Bitbucket repository cannot be a run's repository yet.
- There is no self-hosted or customer-VPC deployment, and we do not publish a compliance report today.
- Compute is metered. Free includes 5 agent-hours a month and Pro 40, each with a weekly ceiling.
- You review the pull request. Rush does not merge for you.

## Questions people actually ask

### Is Amazon Bedrock AgentCore cheaper than E2B?

List prices, read off each vendor's pricing page on 17 October 2026. Amazon Bedrock AgentCore: Runtime $0.0895 per vCPU-hour and $0.00945 per GB-hour; up to $200 Free Tier credit for new AWS customers. E2B: Hobby $0 with a one-time $100 credit; Pro $150 / month plus usage. The units differ, so price the job you run, not the plan.

### Where does Rush fit next to Amazon Bedrock AgentCore and E2B?

Rush runs on E2B and is a finished loop for one job, not a platform: send a task, get the pull request or report back.

## Keep reading

- [Rush vs Amazon Bedrock AgentCore](https://getrush.ai/compare/rush-vs-agentcore.md)
- [Rush vs E2B](https://getrush.ai/compare/rush-vs-e2b.md)
- [Amazon Bedrock AgentCore alternatives](https://getrush.ai/compare/agentcore-alternatives.md)
- [E2B alternatives](https://getrush.ai/compare/e2b-alternatives.md)

## Sources

1. AWS, "Amazon Bedrock AgentCore - AWS", retrieved 2026-10-17. https://aws.amazon.com/bedrock/agentcore/
2. AWS, "Amazon Bedrock AgentCore Pricing - AWS", retrieved 2026-10-17. https://aws.amazon.com/bedrock/agentcore/pricing/
3. AWS, "Amazon Bedrock AgentCore is now generally available", published 2025-10-13. https://aws.amazon.com/about-aws/whats-new/2025/10/amazon-bedrock-agentcore-available/
4. AWS, "Overview (What is Amazon Bedrock AgentCore?)", retrieved 2026-10-17. https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/what-is-bedrock-agentcore.html
5. AWS, "Host agent or tools with Amazon Bedrock AgentCore Runtime", retrieved 2026-10-17. https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html
6. AWS, "AgentCore harness", retrieved 2026-10-17. https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness.html
7. AWS, "Interact with web applications using Amazon Bedrock AgentCore Browser", retrieved 2026-10-17. https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-tool.html
8. E2B, "E2B Pricing", retrieved 2026-10-17. https://e2b.dev/pricing
9. E2B, "E2B | The Enterprise AI Agent Cloud", retrieved 2026-10-17. https://e2b.dev/
10. E2B, "Sandbox persistence", retrieved 2026-10-17. https://docs.e2b.dev/sandbox/persistence
11. E2B, "Claude Code - E2B Docs", retrieved 2026-10-17. https://docs.e2b.dev/agents/claude-code
12. E2B, "Coding Agents - E2B Docs", retrieved 2026-10-17. https://docs.e2b.dev/use-cases/coding-agents
13. E2B, "Available servers - E2B Docs", retrieved 2026-10-17. https://docs.e2b.dev/mcp-gateway/available-servers
14. E2B, "e2b-dev/infra (GitHub README)", retrieved 2026-10-17. https://github.com/e2b-dev/infra
15. Rush, "Rush product requirements", retrieved 2026-09-15. https://getrush.ai/cloud
16. Rush, "Rush pricing (live contract on getrush.ai)", retrieved 2026-09-15. https://getrush.ai/pricing
17. Rush, "Isolation, plainly", retrieved 2026-10-17. https://getrush.ai/docs/concepts/isolation
18. Rush, "Results and proof", retrieved 2026-10-17. https://getrush.ai/docs/concepts/results-and-proof
19. Rush, "Usage and billing", retrieved 2026-10-17. https://getrush.ai/docs/concepts/usage-and-billing
20. Rush, "Rush MCP server", retrieved 2026-10-17. https://getrush.ai/docs/concepts/mcp-server
21. Rush, "Automations", retrieved 2026-10-17. https://getrush.ai/docs/concepts/automations