# 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:** 5\ **Page:** 1
**Author:** ![andremarzo](https://avatars.discourse-cdn.com/v4/letter/a/3da27b/32.png) [@andremarzo](https://discuss.elastic.co/u/andremarzo)\ **Post date:** [June 15, 2021, 9:04pm UTC](https://discuss.elastic.co/t/custom-domain-name/276056/1 "2021-06-15T21:04:08Z")
I am using [cloud.elastic.co](http://cloud.elastic.co/) instance but it provides you long URL to access ES like [XXXXXXXXXXXXXX.us-east-xx.aws.found.io](http://xxxxxxxxxxxxxx.us-east-xx.aws.found.io/) How is possible to use your own domain name with elastic cloud instance? ---
**Author:** ![Imma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/imma/32/32013_2.png) [@Imma](https://discuss.elastic.co/u/Imma)\ **Post date:** [June 15, 2021, 9:15pm UTC](https://discuss.elastic.co/t/custom-domain-name/276056/2 "2021-06-15T21:15:14Z")
I think this blog can help: [Custom Domains and Anonymous Access on Elastic Cloud](https://xeraa.net/blog/2020_custom-domains-and-anonymous-access-on-elastic-cloud/). ---
**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. ---
**Author:** ![Imma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/imma/32/32013_2.png) [@Imma](https://discuss.elastic.co/u/Imma)\ **Post date:** [June 28, 2021, 3:45pm UTC](https://discuss.elastic.co/t/custom-domain-name/276056/4 "2021-06-28T15:45:03Z")
Hi Steven. This is one of the most requested features. [Customer endpoint aliases](https://www.elastic.co/guide/en/cloud/current/ec-regional-deployment-aliases.html) are already supported, which was the first step. What we do not yet support is a custom domain. For that, you would still need a reverse proxy in front of our load balancer/proxies. Unless you don't care about the TLS complain and use a CNAME. We still do not have an ETA on bringing your own domain for Elasticsearch Service, though it's on our radar. Imma. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 26, 2021, 3:45pm UTC](https://discuss.elastic.co/t/custom-domain-name/276056/5 "2021-07-26T15:45:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.