AWS puts each agent workload in its own Nitro VM, at no extra charge

AWS made Nitro Sandboxes available. They are lightweight VMs managed by the Nitro Hypervisor, and each EKS pod, ECS task or VM that uses one gets its own hardware isolation boundary on a shared EC2 instance. The announcement names agent code as a use: Nitro Sandboxes let you "safely execute LLM-generated code in an isolated environment of its own". AWS says enabling them in EKS or ECS is a one-line change, that secrets can be released only to sandboxes that pass cryptographic attestation, and that the feature runs on most Nitro-based instances in all commercial regions at no additional charge. Amazon Linux and Firecracker are supported natively. The page gives no performance figures beyond "near-native EC2 performance".

Why it matters: For a team already on EKS or ECS, a VM boundary per agent task becomes a setting rather than a separate system to run, if the one-line claim holds. The attestation step also gives a concrete way to keep credentials away from any sandbox that has not proven what it is running.