Skip to content
Spinbox is experimental: APIs change and data may be lost. Status lists what is built and what proves it.

Network

View Markdown

Only the proxy, on two ports:

PortFromFor
80AnywhereLet’s Encrypt’s challenge, and a redirect to 443
443proxy_allowed_cidrs (anywhere by default)The dashboard, the API, workspaces’ ports, SSH and terminals

Nothing else in the installation has an inbound rule for the internet. The control plane’s public address is only a way out. A runner has no inbound rule at all. No machine runs SSH.

FromToPortWho the other end is
ProxyControl plane8080TLS under the installation’s CA; the request’s own credential, and for the calls only a proxy makes, the proxy’s token, which it proves again regularly
RunnersControl plane8080TLS under the installation’s CA, and the runner’s token
RunnersProxy (relay)443The relay’s certificate, and a one-time token per session
Proxy, runnersCollector on the control plane4317Only the security group
Control plane, runnersS3443Instance roles; the buckets refuse object requests from anywhere but the VPC’s gateway endpoint

Machines find each other by name in a private zone, spin.internal: cp.spin.internal and proxy.spin.internal, with a ten-second TTL. Each machine writes its own record when it starts serving, so a replaced machine is a record changed, not an address in every configuration.

Runners reach the relay inside the VPC, at proxy.spin.internal, so the proxy’s port 443 does not need to be open to wherever runners are.

Every connection in an installation, opened in the direction of its arrow; nothing else is let in.
Every connection in an installation, opened in the direction of its arrow; nothing else is let in. Its source.

Set proxy_allowed_cidrs to the networks your users are on:

proxy_allowed_cidrs = ["203.0.113.0/24", "198.51.100.10/32"]

Port 80 stays open to everyone, for Let’s Encrypt.

Every machine has a public address in a public subnet, and reaches S3 through the free gateway endpoint. A NAT gateway is billed by the hour in each zone that has one, plus a charge for every gigabyte, before any workspace runs: one alone costs most of what the two machines that run all the time do, and the subnets span several zones. A public address is not an open door: the security groups decide what reaches each machine, and for all but the proxy that is nothing from outside the VPC.

The VPC’s flow log goes to CloudWatch for 30 days (log_retention_days); flow_logs = false turns it off, and dns_query_logs = true turns on Route 53 Resolver’s query log. The three are variables of the control plane’s module, which the root module leaves at their defaults.

A workspace’s own traffic is controlled separately, by its network policies, on the runner. See Network and egress.

Installations run Spinbox v20261027.01; the reference is generated from spin v20261114.01 (51f7e0dea). This page as Markdown, for a model or a terminal.