Skip to content

PLAT-238: Workspace-level network egress policy

Statement

The platform shall deliver the zero-egress (no-NAT) range posture (#1171) as a workspace-level policy: an administrator shall set an egress policy on a workspace that the range provisioning path enforces identically on AWS and GCP, and an SPA control shall expose the setting. Enforcement shall use each cloud's native network primitives rather than a hand-rolled egress filter, and the compatibility default shall preserve existing range behavior.

Rationale

Program #1321 specifies zero-egress (#1171) be delivered as a workspace-level policy so shared-infrastructure operators can enforce it per workspace. It is not yet implemented as workspace policy. Using each cloud's native primitives keeps AWS/GCP parity and avoids a hand-rolled control (PLAT-241).

Traceability

  • IMPLEMENTS → GITHUB_ISSUE 1945
  • IMPLEMENTS → CODE shifter/engine/provisioner/gcp_range_cell_shared_nat.py (Explicit shared-VPC NAT enrollment preserves zero-egress ranges and bounded GCP capacity)
  • TESTS → TEST shifter/engine/provisioner/tests/test_gcp_shared_nat.py (Shared-NAT capacity, zero-egress, and migration replay coverage)