AWS launches Nitro Sandboxes: each EKS pod, ECS task or lightweight VM gets its own hardware-isolated VM, enabled with a one-line change at no additional charge
Running LLM-generated code multi-tenant on one EC2 instance, safely. How strong the isolation is, how to turn it on and what it costs.
// Key points
- Each workload gets its own VM managed by the Nitro Hypervisor at near-native EC2 performance, so untrusted, multi-tenant or regulated workloads can share one instance safely.
- Cryptographic attestation means secrets are released only to Nitro Sandboxes that have proven their integrity.
- In EKS or ECS it is a one-line change, with Pod Identity, VPC CNI, EBS, EFS, S3 and CloudWatch working as usual; on EC2 you can bring your own AMI and VMM, with Amazon Linux and Firecracker supported natively.
- It is available on most Nitro-based EC2 instances in all commercial regions at no additional charge.
Builder's takeRead with the 11-07 item on Claude Code running one microVM per task on AgentCore, and the default isolation unit for agent code is moving from containers to VMs. If your backend runs model-written scripts, as PandaClaws' data processing does, move those jobs to a separate node group on Nitro Sandboxes first, then see whether secrets can be released by attestation.
// Background · from #AI agents
Full timeline →- Nov 10 Amazon Bedrock Managed Knowledge Base adds single-shot RAG and retrieval-only modes to the same API as its multi-step agentic retrieval
- Nov 9 Google measures agent distraction: 13% of sessions meet bug-referencing TODOs, and detoured sessions take 70% more steps and 77% more tokens
- Nov 9 Greenlight builds Luna, a security operations agent on AgentCore: up to 4,000 cases a month, more than 90% resolved without human intervention