hn.today

AWS Nitro Sandboxes: Hardware-Enforced Workload Isolation on Amazon EKS

aws.amazon.com9 points1 comments
Screenshot of AWS Nitro Sandboxes: Hardware-Enforced Workload Isolation on Amazon EKS

AWS Nitro Sandboxes for Amazon EKS are designed to give Kubernetes pods the isolation of separate EC2 instances without requiring a dedicated machine for every sensitive workload. The approach addresses risks from shared host kernels, especially as AI agents execute generated code, SaaS platforms run multiple customers on shared clusters, regulated organizations need verifiable protections, and CI/CD jobs use elevated privileges. Instead of relying solely on patched kernels or costly one-workload-per-machine deployments, each sandboxed pod runs in a lightweight virtual machine with its own operating system kernel and a hardware-enforced boundary from the host and neighboring pods.

The offering has two modes. Isolated Mode protects the host and other pods from activity inside a workload; Confidential Mode also treats the machine operator as untrusted, using cryptographic attestation to verify the running system image and Cedar policy before AWS KMS permits decryption. Nitro’s hardware-enforced CPU and memory slices prevent neighboring workloads from accessing a pod’s memory or state, while configurable throttles limit shared resources such as network bandwidth, disk I/O, DNS, logs, and connection tracking. On EKS Auto Mode, users enable sandboxing with one pod-spec change; standard EKS requires a configured AMI. Container images, common EKS integrations, and Kubernetes operations remain familiar, and the system passes Kubernetes conformance tests.

Read on aws.amazon.com1 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Security

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.