Restrict worker pool registration to specific IPs

Thanks for the suggestion! This could indeed be a helpful extra layer of security. That said, we’d love to understand the underlying concern a bit more clearly.

What’s the specific risk or scenario you’re trying to guard against with IP restrictions at registration time? Given that each worker pool already requires a unique token, we’re curious what additional protection IP-based controls would provide in your environment.

Are you trying to enforce that registration only happens from known networks (e.g., corporate VPCs)? Is the concern around credential misuse, auditability, or limiting setup to trusted infra? Or something else?

If you’re open to sharing more about the trigger or goal behind the request, we’d love to better understand the job to be done—so we can evaluate whether IP restrictions are the best tool, or whether something different might get you there faster.