Changelog
Destination proxies
In short
Route webhook, RabbitMQ and Kafka deliveries through proxies
Self-hosted Outpost can now route webhook, RabbitMQ and Kafka destination connections through an HTTP CONNECT proxy, so destinations that allowlist source IPs see the proxy's address. Set DESTINATIONS_PROXY_URL to a proxy URL, or to several whitespace-separated URLs to chain proxies in order. TLS runs end to end between Outpost and the broker.
The same applies to ingestion: PUBLISH_PROXY_URL routes a RabbitMQ publish queue connection through a proxy chain in the same format.
DESTINATIONS_ is deprecated but still works, and overrides the new variable for webhooks. See the forward proxy guide.
Destination proxies are available now in v1.6.0.