Amazon Bedrock AgentCore Code Interpreter vs Maritime

Amazon Bedrock AgentCore Code Interpreter

Each session runs in its own microVM with 2 vCPU, 8 GB and a 10 GB disk for up to eight hours, and IAM can scope access to one interpreter. Sessions cannot be paused or resumed, and an AWS account with IAM set-up is needed before a first call.

Maritime

Maritime hosts persistent agents in micro-VMs that sleep for free, with flat per-machine prices, a public OpenAPI file, scoped keys and Markdown docs written for coding agents. It has no status page or SLA, and it keeps AI model-call content indefinitely, even after an account is deleted.

Amazon Bedrock AgentCore Code Interpreter

1. Start a session with StartCodeInterpreterSession, then pass its id in the x-amzn-code-interpreter-session-id header on every InvokeCodeInterpreter call
2. Set sessionTimeoutSeconds when starting. The default is 900 seconds and the maximum is eight hours, and the session ends itself at the timeout
3. Stop sessions when done. Billing runs per second while code is busy, and a session left open counts against the 1,000 concurrent-session quota
4. Use bedrock-agentcore 1.18.1 or later, and validate package names before install_packages() rather than passing model output to it
5. Retry ThrottlingException (429) and InternalServerException (500) with exponential backoff, and treat ServiceQuotaExceededException, returned as HTTP 402, as a quota to raise

Maritime

1. Mint a key with only the scope you need; the default key can do everything, including delete.
2. Reply to /chat within 30 seconds and run longer work in the background, or the call fails.
3. Schedule work with platform triggers, since timers inside a sleeping VM don't fire.
4. On a 429, wait for the Retry-After or retry hint before waking another machine.
5. Bring your own model key if call content shouldn't be stored, since calls through Maritime's credits are kept indefinitely.