Changelog

Sandboxes on EKS with AWS Nitro Sandboxes

Sandboxes on EKS now run in AWS Nitro Sandboxes, the isolated-sandbox RuntimeClass of EKS Auto Mode. Untrusted code your app starts, such as an agent's tool calls or a customer's script, gets its own sandboxed runtime instead of the node's ordinary container runtime.

Your code doesn't change. The Sandbox you declare in alien.ts and the calls in your workload are the same on every platform:

api/src/run.ts
import { sandbox } from "@alienplatform/sdk"

const box = sandbox("agent")
const { sandbox: agent } = await box.getOrCreate("task-42", {
  egress: { allow: ["api.example.com"] },
})

for await (const frame of box.runCommand(agent.sandboxId, "python3", { args: ["job.py"] })) {
  if (frame.kind === "stdout") process.stdout.write(frame.data)
}

The chart picks the runtime from the cluster's Kubernetes version:

ClusterRuntime
EKSAWS Nitro Sandboxes (isolated-sandbox)
GKEgVisor (gvisor)
AKSKata VM isolation. Set sandbox.runtimeClassName: kata-vm-isolation.
On-premisesThe gVisor or Kata class your administrator installed. Set sandbox.runtimeClassName.
  • Requirements: EKS Auto Mode on Kubernetes 1.36 or later. EKS clusters Alien creates start on 1.36.
  • Argo CD: Argo CD renders the chart without the cluster version, so set sandbox.runtimeClassName: isolated-sandbox in your values.
  • Boundary: the Alien Operator refuses a RuntimeClass that isn't sandboxed. Sandbox pods get no service account token, and a sandbox starts only after its NetworkPolicy is proven in force.
  • Sessions: getOrCreate with your own id, reconnecting from another process, long interactive commands, preview, and "none", "internet", or allowlist egress all work as on the other platforms.

Read the docs →