# AWS Nitro Sandboxes give pods, tasks and agents their own hardware-isolated VM

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

AWS announced AWS Nitro Sandboxes on 9 November 2026: lightweight VMs managed by the Nitro Hypervisor for an EKS pod, ECS task or VM, including AI agents running inside them. Each workload gets its own isolation boundary, and AWS says secrets are released only after attestation.

AWS announced on 9 November 2026 that AWS Nitro Sandboxes are available as lightweight VMs managed by the Nitro Hypervisor. They can be used for an Amazon EKS pod, an Amazon ECS task or a VM, including AI agents running inside them, each in its own hardware-isolated virtual machine. AWS says this allows untrusted, multi-tenant or regulated workloads to share the resources of a single instance.

AWS also says workloads can be validated through cryptographic attestation so that secrets are released only to Nitro Sandboxes that have proven their integrity, and that LLM-generated code can run in an isolated environment of its own. Enabling it in EKS or ECS is described as a one-line change, with Pod Identity and VPC controls staying native. It is available on most Nitro-based EC2 instances at no extra charge.

## Related pages

- [Amazon Quick adds smart approvals for actions that agents take](/news/quick-smart-approvals-agentic-actions/)
- [WorkSpaces for AI agents adds OAuth sessions inside existing network boundaries](/news/workspaces-for-ai-agents-oauth-sessions/)
- [Act Security and HUB International build a no-credentials coding agent environment](/news/act-hub-international-agentcore-coding-agents/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/11/nitro-sandboxes-eks-ecs-ec2/ (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/news/nitro-sandboxes-eks-ecs-ec2-agents/
