# Using your own domain cname to access cloud elastic instance?

**URL:** <https://discuss.elastic.co/t/using-your-own-domain-cname-to-access-cloud-elastic-instance/142024>\
**Category:** Elasticsearch\
**Created:** [July 28, 2018, 11:11am UTC](https://discuss.elastic.co/t/using-your-own-domain-cname-to-access-cloud-elastic-instance/142024 "2018-07-28T11:11:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![agonzalez](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@agonzalez](https://discuss.elastic.co/u/agonzalez)\
**Post date:** [July 28, 2018, 11:11am UTC](https://discuss.elastic.co/t/using-your-own-domain-cname-to-access-cloud-elastic-instance/142024/1 "2018-07-28T11:11:14Z")

</div>

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)

I tried to set a DNS CNAME like "[es.mycompany.com](http://es.mycompany.com)" to mask the name but then trying to access elasticsearch using my domain doesnt work.

How is possible to use your own domain name with elastic cloud instance?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 28, 2018, 11:29am UTC](https://discuss.elastic.co/t/using-your-own-domain-cname-to-access-cloud-elastic-instance/142024/2 "2018-07-28T11:29:41Z")

</div>

You can't. Read:

[https://www.elastic.co/guide/en/cloud/saas-release/ec-faq.html#faq-dns](https://www.elastic.co/guide/en/cloud/saas-release/ec-faq.html#faq-dns)

---

<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:** [August 25, 2018, 11:29am UTC](https://discuss.elastic.co/t/using-your-own-domain-cname-to-access-cloud-elastic-instance/142024/3 "2018-08-25T11:29:42Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 21, 2020, 8:34am UTC](https://discuss.elastic.co/t/using-your-own-domain-cname-to-access-cloud-elastic-instance/142024/4 "2020-04-21T08:34:00Z")

</div>

As the link has been removed ans some people still find this answer, I'm linking to another more recent post which has more information:

> [@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.