>
> Over the past few weeks we have seen several users trying to run multiple fleet-…servers. This issue is to discuss the different scenarios and share an initial thoughts on how we could approach this. The goal is to come a conclusion and feed the information in the documentation and have it guideline for future features.
>
> \# Core concepts
>
> \* No load balancing: It is not the Elastic Agent jobs to load balance between multiple fleet-servers. This must be done at the infrastructure level through proxy or DNS.
> \* Fail over: An Elastic Agent supports multiple fleet-server urls as failover. By default the first url is picked.
> \* All info is shared across fleet-servers: Each fleet-server has always the same information no matter where it is deployed.
>
> \# Scenarios
>
> Below is a list of scenarios which should describe the expected behaviours to follow the above core concepts. Not all scenarios are supported today.
>
> \## Scenario 1: Multiple fleet-servers, all Elastic Agent connect to all fleet-servers
>
> In scenario 1 the users had multiple fleet-servers for redundancy or scale purpose. The user is expected to setup a proxy in front of the fleet-servers or use DNS to access the multiple fleet-servers. In the Fleet UI, a single fleet-server url is used.
>
> \## Scenario 2: Elastic Cloud only
>
> The user connects all its Elastic Agent to the fleet-server in Elastic Cloud. As ESS already has a proxy in front and allows to spin up redundant fleet-servers, the setup is already as expected today.
>
> \## Scenario 3: Elastic Cloud fleet-server and on prem
>
> The users is using Elastic Cloud with the fleet-server but also runs its on prem fleet-server to have the fleet-server closer to its Elastic Agents. By default the user wants to have its local fleet-servers to be used. In the Fleet UI, the user puts and additional fleet-server url before the Elastic Cloud fleet-server url. The user defined URL is the one used by default. In case the local fleet-server url is not reachable, Elastic Agents fall back to the Elastic Cloud fleet-server url.
>
> The local fleet-server is expected to have the version in sync with the hosted fleet-server.
>
> \## Scenario 4: Multi policy with multi data center
>
> In this scenario the user has multiple data centers with local fleet-servers and specific policies to each data center. In the Fleet UI, a global fleet-server is specified and in addition a fleet-server per policy can be specified. The fleet-server specified in the policy is the first in the list so it will be picked as the default for all Elastic Agent which are part of the policy.
Can anybody tell me if it is possible to use just one URL to connect to all fleet servers?
It seems like it is not possible at the moment or any elastic agent needs to connect always to the same fleet server?
Thanks in advance!
greetings
---
### Author:  [@mtojek](https://discuss.elastic.co/u/mtojek)
#### Post date: [March 21, 2022, 2:58pm UTC](https://discuss.elastic.co/t/load-balanced-access-to-fleet-servers/300210/2 "2022-03-21T14:58:53Z")
Hm... the error doesn't look like something is wrong with Fleet Server, but rather with your load balancing solution. Could you please try to configure any Nginx of HAProxy instead (temporarily) and make sure that load-balanced Fleet Servers communicate well with the agent?
---
### Author:  [@fuphil](https://discuss.elastic.co/u/fuphil)
#### Post date: [March 22, 2022, 7:10am UTC](https://discuss.elastic.co/t/load-balanced-access-to-fleet-servers/300210/3 "2022-03-22T07:10:41Z")
When I call the api status via the loadbalanced address on haproxy, I get a healthy state.
I would assume this is enough to verify the connection, isn't it?
> curl [https://loadbalancedip:8220/api/status](https://loadbalancedip:8220/api/status)
```auto
{"name":"fleet-server","status":"HEALTHY"}
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 19, 2022, 9:11am UTC](https://discuss.elastic.co/t/load-balanced-access-to-fleet-servers/300210/4 "2022-04-19T09:11:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.