# Customize Kibana URL and DNS

**URL:** <https://discuss.elastic.co/t/customize-kibana-url-and-dns/284744>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [September 21, 2021, 3:13pm UTC](https://discuss.elastic.co/t/customize-kibana-url-and-dns/284744 "2021-09-21T15:13:36Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![netjammr](https://avatars.discourse-cdn.com/v4/letter/n/b3f665/32.png) [@netjammr](https://discuss.elastic.co/u/netjammr)\
**Post date:** [September 21, 2021, 3:13pm UTC](https://discuss.elastic.co/t/customize-kibana-url-and-dns/284744/1 "2021-09-21T15:13:36Z")

</div>

I am looking at options for customizing the Kibana URL for an ECE deployment. As an example, if under Platform \> Settings the "Deployments domain name" is "[myece.mydomain.com](http://myece.mydomain.com)", I understand that the Kibana URL would be some random GUID appended to the Deployment domain name ([someGUID.myece.mydomain.com](http://someGUID.myece.mydomain.com)). If I create an unrelated CNAME DNS record that is more readable ([mykibana.mydomain.com](http://mykibana.mydomain.com)) and point that to our LB, will ECE proxies still forward traffic to our Kibana? We will have a wildcard cert for \*[mydomain.com](http://mydomain.com) loaded under Platform \> Settings \> TLS certificates \> Proxy.

Thank you,  
Fidel

---

<div class="post-metadata">

**Author:** ![Daniel\_Battaglia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_battaglia/32/49649_2.png) [@Daniel\_Battaglia](https://discuss.elastic.co/u/Daniel_Battaglia)\
**Post date:** [September 21, 2021, 4:32pm UTC](https://discuss.elastic.co/t/customize-kibana-url-and-dns/284744/2 "2021-09-21T16:32:05Z")

</div>

ECE (as well as Elastic Cloud) does offer a feature Deployment Aliases. This allows you to give a custom name that will be used in the Kibana URL in place of the GUID. So, for example, if you have "[myece.mydomain.com](http://myece.mydomain.com)" as your configured Deployments domain name, and you set your alias to "my-kibana", the URL will be "[https://my-kibana.myece.mydomain.com](https://my-kibana.myece.mydomain.com)".

Below are the docs for setting up and using this feature in ECE:

> **[Custom endpoint aliases | Elastic Cloud Enterprise Reference \[2.11\] | Elastic](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-regional-deployment-aliases.html)**

> **[Custom endpoint aliases | Elastic Cloud Enterprise Reference \[2.11\] | Elastic](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-regional-deployment-aliases.html)**

---

<div class="post-metadata">

**Author:** ![netjammr](https://avatars.discourse-cdn.com/v4/letter/n/b3f665/32.png) [@netjammr](https://discuss.elastic.co/u/netjammr)\
**Post date:** [September 21, 2021, 6:00pm UTC](https://discuss.elastic.co/t/customize-kibana-url-and-dns/284744/3 "2021-09-21T18:00:20Z")

</div>

Hi @Daniel_Battaglia - unfortunately I don't think this is a feature we can use since we are still at version 2.8.1. Is the scenario I originally described possible through the use of CNAME records and LB forwarding traffic?

---

<div class="post-metadata">

**Author:** ![Daniel\_Battaglia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_battaglia/32/49649_2.png) [@Daniel\_Battaglia](https://discuss.elastic.co/u/Daniel_Battaglia)\
**Post date:** [September 21, 2021, 7:29pm UTC](https://discuss.elastic.co/t/customize-kibana-url-and-dns/284744/4 "2021-09-21T19:29:55Z")

</div>

That should work as well. We have some documentation around this:

> **[Load balancers | Elastic Cloud Enterprise Reference \[2.11\] | Elastic](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-load-balancers.html)**

---

<div class="post-metadata">

**Author:** ![Jugsofbeer](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@Jugsofbeer](https://discuss.elastic.co/u/Jugsofbeer)\
**Post date:** [October 3, 2021, 3:31am UTC](https://discuss.elastic.co/t/customize-kibana-url-and-dns/284744/5 "2021-10-03T03:31:11Z")

</div>

Why make the load balancer work harder though?

Wouldnt an ece upgrade be better and give you features and bug fixes you can enjoy?

---

<div class="post-metadata">

**Author:** ![netjammr](https://avatars.discourse-cdn.com/v4/letter/n/b3f665/32.png) [@netjammr](https://discuss.elastic.co/u/netjammr)\
**Post date:** [October 4, 2021, 2:47pm UTC](https://discuss.elastic.co/t/customize-kibana-url-and-dns/284744/6 "2021-10-04T14:47:18Z")

</div>

We have specific constraints that prevent us from upgrading to the latest ECE version at the moment and load balancers are part of the reference architecture.

---

<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:** [October 18, 2021, 2:47pm UTC](https://discuss.elastic.co/t/customize-kibana-url-and-dns/284744/7 "2021-10-18T14:47:30Z")

</div>

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