# Custom Domain Name **URL:** \ **Category:** Kibana\ **Created:** [June 15, 2021, 9:04pm UTC](https://discuss.elastic.co/t/custom-domain-name/276056 "2021-06-15T21:04:08Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![stexxen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stexxen/32/68327_2.png) [@stexxen](https://discuss.elastic.co/u/stexxen)\ **Post date:** [June 25, 2021, 8:08am UTC](https://discuss.elastic.co/t/custom-domain-name/276056/3 "2021-06-25T08:08:34Z")
Hi @Imma I do not think that is a great solution it's effectively saying put an nginx reverse proxy in front of the load balanced and resilient infrastructure that you are buying from Elastic Cloud. I notice on previous subjects relating to this (going back 18 months+) it was mentioned that this ability was coming. Do you have any further details? Nov 2019 > [@Use own domain as Kibana URL](https://discuss.elastic.co/t/use-own-domain-as-kibana-url/207703/2): > > Hi @ingoAlmeida, It's not yet possible, see [more info here](https://www.elastic.co/guide/en/cloud/current/ec-faq.html#ec_technical) (same rules apply to Kibana endpoint as well). The only workaround I'm aware of is to have your own proxy infrastructure in front of Elastic Cloud cluster. Having said that I know this issue is tracked and in discussion right now. Best, Oleg Jan 2020 > [@Elastic Cloud custom domain?](https://discuss.elastic.co/t/elastic-cloud-custom-domain/214853/3): > > Hey Alberto It's not fully supported today as the browser will complain about TLS as the certificate won't be for the same domain. You can define a CNAME. If your cluster is for example abcdef.us-east-1.aws.found.io you can add a CNAME my-es-cluster in your DNS which goes to abcdef.us-east-1.aws.found.io. It will be fully supported in the future AFAIK. But no ETA on this though. Thanks, Steven. --- _[View the full topic](https://discuss.elastic.co/t/custom-domain-name/276056)._