Static Outbound IPs currently assigns a fixed pool of 3 IPs and load-balances traffic randomly across all of them, with no way to restrict which IPs are actually used.

This breaks integrations with financial/banking APIs (e.g., stock brokers) that require IP whitelisting but only allow whitelisting a small, fixed number of IPs (often just 1-2) per API key — some providers, for security/compliance reasons, will not whitelist more than 2 IPs at all.

Right now, this means any service with 3 static IPs but only 2 approved by a downstream provider will see ~33% of its outbound requests randomly fail with an "IP not recognized" error — a serious problem for anything transactional (e.g., placing real trades).

Requested feature: allow choosing to use only a subset (e.g., 1 or 2) of the assigned static IPs for actual outbound traffic, or let us request a smaller fixed pool size (e.g., exactly 2 IPs) instead of always 3.