From ec2a8660297d5fc6dfedcee38b4f95d5daab638b Mon Sep 17 00:00:00 2001 From: Harrison Ravazzolo <38767391+harrisonravazzolo@users.noreply.github.com> Date: Wed, 8 Jan 2025 14:13:46 -0800 Subject: [PATCH] Update proxy doc in reference architecture (#25230) Small change from a slack convo - https://fleetdm.slack.com/archives/C019WG4GH0A/p1736282697358929 Co-authored-by: Harrison John --- docs/Deploy/Reference-Architectures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Deploy/Reference-Architectures.md b/docs/Deploy/Reference-Architectures.md index 70dc4303ede6..20e1b7702a5e 100644 --- a/docs/Deploy/Reference-Architectures.md +++ b/docs/Deploy/Reference-Architectures.md @@ -111,7 +111,7 @@ In order for osqueryd clients to connect, the connection to Fleet must use TLS. ## Using a proxy -If you are in an enterprise environment where Fleet is behind a proxy and you would like to be able to retrieve vulnerability data for [vulnerability processing](https://fleetdm.com/docs/using-fleet/vulnerability-processing#vulnerability-processing), it may be necessary to configure the proxy settings. Fleet automatically uses the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables. +In enterprise environments where Fleet operates behind a proxy, you may need to configure proxy settings to enable services requiring outbound traffic, such as [vulnerability processing](https://fleetdm.com/docs/using-fleet/vulnerability-processing#vulnerability-processing) or [device management](https://fleetdm.com/device-management). Fleet automatically uses the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables. For example, to configure the proxy in a systemd service file: