coder/docs/ai-coder/agent-firewall/nsjail/ecs.md

nsjail on ECS

Note

Agent Firewall requires the AI Governance Add-On. As of Coder v2.32, deployments without the add-on will not be able to access Agent Firewall.

This page describes the runtime and permission requirements for running Agent Firewall with the nsjail jail type on Amazon ECS.

Runtime & Permission Requirements for Running Agent Firewall in ECS

The setup for ECS is similar to nsjail on Kubernetes; that environment is better explored and tested, so the Kubernetes page is a useful reference. On ECS, requirements depend on the node OS and how ECS runs your tasks. The following examples use ECS with Self Managed Node Groups (EC2 launch type).

---

Example 1: ECS + Self Managed Node Groups + Amazon Linux

On Amazon Linux nodes with ECS, the default Docker seccomp profile enforced by ECS blocks the syscalls needed for Agent Firewall. Because it is difficult to disable or modify the seccomp profile on ECS, you must grant SYS_ADMIN (along with NET_ADMIN) so that Agent Firewall can create namespaces and run nsjail.

Task definition (Terraform) — linuxParameters:

container_definitions = jsonencode([{
  name      = "coder-agent"
  image     = "your-coder-agent-image"

  linuxParameters = {
    capabilities = {
      add = ["NET_ADMIN", "SYS_ADMIN"]
    }
  }
}])

This gives the container the capabilities required for nsjail when ECS uses the default Docker seccomp profile.