# Fleet: Override Elasticsearch URL at policy level

**URL:** <https://discuss.elastic.co/t/fleet-override-elasticsearch-url-at-policy-level/275982>\
**Category:** Beats\
**Tags:** fleet, elastic-agent\
**Created:** [June 15, 2021, 11:00am UTC](https://discuss.elastic.co/t/fleet-override-elasticsearch-url-at-policy-level/275982 "2021-06-15T11:00:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nugroho-expereo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nugroho-expereo/32/78333_2.png) [@nugroho-expereo](https://discuss.elastic.co/u/nugroho-expereo)\
**Post date:** [June 15, 2021, 11:00am UTC](https://discuss.elastic.co/t/fleet-override-elasticsearch-url-at-policy-level/275982/1 "2021-06-15T11:00:23Z")

</div>

Hi All,

Is it possible to override Elasticsearch URL for fleet on policy Level? I see in the UI we only have global setting. We use Elastic Cloud service.

Use Case:

- For on premise agent it should connect to the public URL
- For agent in AWS we want to have it connected via Private Link URL (_.vpce._)

If we enter both URLs we have a lot of error messages on on premise elastic agent because private link DNS cannot be resolved.

It would be nice to be able to override Elasticsearch URLs at policy level.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/a/0aca5432a8c34dd93948841dfc95c1b6b723128d.png)

Thank you.

Regards,  
Nugroho

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [June 15, 2021, 12:10pm UTC](https://discuss.elastic.co/t/fleet-override-elasticsearch-url-at-policy-level/275982/2 "2021-06-15T12:10:58Z")

</div>

HI @nugroho-expereo Unfortunately we don't have that feature yet. One related issue you can find here: [[Fleet] Support configuring and referencing multiple outputs · Issue #90414 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/90414) Maybe you can chime in there with your use case.

I'm pretty sure we also have somewhere a more recent issue tracking this per policy but could not find it right now. Will link the two together when I find it.

---

<div class="post-metadata">

**Author:** ![nugroho-expereo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nugroho-expereo/32/78333_2.png) [@nugroho-expereo](https://discuss.elastic.co/u/nugroho-expereo)\
**Post date:** [June 16, 2021, 3:04pm UTC](https://discuss.elastic.co/t/fleet-override-elasticsearch-url-at-policy-level/275982/3 "2021-06-16T15:04:00Z")

</div>

Thank you @ruflin . I have added my comment to the issue.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 14, 2021, 5:04pm UTC](https://discuss.elastic.co/t/fleet-override-elasticsearch-url-at-policy-level/275982/4 "2021-07-14T17:04:18Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.