Skip to content

Add instructions for deploying fleet-server behind load balancer #5273

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
michel-laterman wants to merge 4 commits into
base: main
Choose a base branch
from
+23 −0
Open

Add instructions for deploying fleet-server behind load balancer #5273

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
40151c8
Add instructions for deploying fleet-server behind load balancer
michel-laterman Feb 23, 2026
78766e6
Get rid of instances of i.e.
michel-laterman Feb 23, 2026
1beafdc
change example wording
michel-laterman Feb 24, 2026
5cd3f3b
Fix note formatting
michel-laterman Feb 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions reference/fleet/add-fleet-server-on-prem.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,6 +153,29 @@ You can update your {{fleet-server}} configuration in {{kib}} at any time by goi
* Specify proxy URLs to use for {{fleet-server}} or {{agent}} outputs.


## {{fleet-server}} setup using a load balancer [fleet-server-setup-using-a-load-balancer]

When deploying {{fleet-server}} behind a load balancer/reverse proxy the following steps need to be taken:

1. Create a certificate that contains DNS entries for the agent-facing load balancer, and the hostnames it routes to. For example, the load balancer `fleet.example.com` will route to hostnames `fleet1.example.com`, and `fleet2.example.com`.

2. Configure the load balancer/reverse proxy.
* The load balancer directs traffic to all {{fleet-server}} instances.
* Ensure that timeouts for the load balancer have been raised to support the long-polling connections {{agents}} create when checking in to {{fleet-server}}.
The default timeout for long-poll in {{fleet-server}} is 5 minutes, the {{fleet-server}}'s write timeout, and the {{agent}}'s request timeout are set to 10 minutes. The load balancer timeout should be set to 10 minutes.
* It's recommended to configure the load balancer with TLS pass through.

::::{note}
Starting with {{stack}} v9.4 or later, the {{fleet-server}} status API `GET /api/status` may be used to determine instance health from the load balancer.
Copy link
Contributor Author

@michel-laterman michel-laterman Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requires the change in elastic/elastic-agent#12917, the change may be back-ported if we need.

::::

3. Add the load balancer (example: `https://fleet.example.com:8220`) as a {{fleet-server}} host under the **Settings** tab in {{fleet}}.

4. Install {{fleet-server}} on each backing host using the in-product instructions which should specify the load balancer as the URL.

5. Enroll other {{agent}} instances using the load balancer URL.


## Troubleshooting [add-fleet-server-on-prem-troubleshoot]

If you’re unable to add a {{fleet}}-managed agent, click the **Agents** tab and confirm that the agent running {{fleet-server}} is healthy.
Expand Down
Loading