Add upstream proxy feature#208
Open
eraow wants to merge 1 commit into
Open
Conversation
eraow
marked this pull request as ready for review
July 16, 2026 16:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an
--upstream-proxyoption so Boundary can forward its own outboundrequests through an HTTP(S) proxy. This makes Boundary usable in environments
that only allow internet access via a corporate proxy.
Motivation
I want to run Boundary behind a corporate proxy. Without this option, Boundary
connects directly to upstream hosts, which fails when direct egress is blocked
and only a proxy is permitted.
What this does
--upstream-proxy <URL>(envBOUNDARY_UPSTREAM_PROXY, YAMLupstream_proxy), e.g.http://proxy.corp:3128.given proxy instead of connecting directly. Allow-rule evaluation and audit
logging still happen first — the upstream proxy only receives already-allowed
requests.
HTTP_PROXYsetting. The confined child still sends traffic to Boundary first.Usage
boundary --upstream-proxy http://proxy.corp:3128 \ --allow "domain=github.com" -- curl https://github.comManual verification
PASS (allowed domain)
BLOCK (disallowed domain — never reaches the upstream proxy)