# ECE URL Change **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [June 27, 2019, 8:57pm UTC](https://discuss.elastic.co/t/ece-url-change/187930 "2019-06-27T20:57:37Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [June 27, 2019, 8:57pm UTC](https://discuss.elastic.co/t/ece-url-change/187930/1 "2019-06-27T20:57:37Z")
I'm looking at the ECE documentation, and "Change endpoint URLs" section is not clear to me. [https://www.elastic.co/guide/en/cloud-enterprise/current/ece-administering-endpoints.html](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-administering-endpoints.html) By default, cluster and Kibana endpoint URLs are constructed according to the following pattern, where `CLUSTER_ID` and `LOCAL_HOST_IP` are values that depend on your specific installation: http://CLUSTER\_ID.LOCAL\_HOST\_IP.ip.es.io:9200 https://CLUSTER\_ID.LOCAL\_HOST\_IP.ip.es.io:9243 For example: [http://2882c82e54d4361.us-west-5.aws.found.io:9200](http://2882c82e54d4361.us-west-5.aws.found.io:9200) [https://2882c82e54d4361.us-west-5.aws.found.io:9243](https://2882c82e54d4361.us-west-5.aws.found.io:9243) How "[found.io](http://found.io)" URL was produced in the above example? Is just an example of another URL? Why they didn't use the same example as above ("[es.io](http://es.io)")? Do I need to keep [es.io](http://es.io) or [found.io](http://found.io) after I change the internal IP to a name of the hostname in AWS or GCP? ---
**Author:** ![zanbel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zanbel/32/20678_2.png) [@zanbel](https://discuss.elastic.co/u/zanbel)\ **Post date:** [June 28, 2019, 10:10am UTC](https://discuss.elastic.co/t/ece-url-change/187930/2 "2019-06-28T10:10:40Z")
Hey @daniel_a, Maybe the [found.io](http://found.io) is a bit confusion here but you don't need to keep it. For example in my ECE environment the default deployments URL is: `..ip.es.io:9243` and I can change this configuration to a more user friendly endpoint like: `.ece.acme.com` by replacing `.ip.es.io` with `ece.acme.com` in Platform \>\> Settings page. This means I also need to provide the relevant wild card certificate which I can upload in the same page. ---
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [June 28, 2019, 4:31pm UTC](https://discuss.elastic.co/t/ece-url-change/187930/3 "2019-06-28T16:31:23Z")
Why the [es.io](http://es.io) part has been added to the URL? I have an ECE deployment in GCP, and I use 10.x.x.x for the deployment. Let's say that my Kibana sits at 10.10.10.1, why can't I access Kibana by going directly to 10.10.10.1:9243, but I'll need to add that extra part to the URL ([10.10.10.1.ip.es.io:9243](http://10.10.10.1.ip.es.io:9243)) to be able to access it. Can you please elaborate on the [es.io](http://es.io) part a bit more? This seems to be a TLD here (similar to .com or .org), but I don't have a DNS record for it or never created one, and I'm not going outside (to the Internet). --Thanks ---
**Author:** ![zanbel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zanbel/32/20678_2.png) [@zanbel](https://discuss.elastic.co/u/zanbel)\ **Post date:** [June 29, 2019, 10:28am UTC](https://discuss.elastic.co/t/ece-url-change/187930/4 "2019-06-29T10:28:23Z")
All requests to Elasticsearch, Kibana, APM server, etc. are routed through our proxy service. You cannot ensure a specific Kiabana instance is available over a specific IP, and even if you find the container IP in various scenarios we will start a new Kibana container and kill the old one so the IP will change. That's why the routing is managed by the proxy and why the endpoint is constructed with the Kibana UUID which doesn't change. We are planning to introduce a way for users to define deployment aliases which will support setting human friendly string to be used instead of the UUID. I think that will address your use case. ---
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [June 30, 2019, 8:33pm UTC](https://discuss.elastic.co/t/ece-url-change/187930/5 "2019-06-30T20:33:05Z")
In this case, how do I request a CRQ certificate request if the domain for Kibana and proxies are hosted on [es.io](http://es.io) domain? What's the best way to sign the certs for the internal IPs sitting on this domain? ---
**Author:** ![zanbel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zanbel/32/20678_2.png) [@zanbel](https://discuss.elastic.co/u/zanbel)\ **Post date:** [July 1, 2019, 8:16am UTC](https://discuss.elastic.co/t/ece-url-change/187930/6 "2019-07-01T08:16:17Z")
We recommend using a wildcard certificate as mentioned in the following [page](https://www.elastic.co/guide/en/cloud-enterprise/2.2/ece-wildcard-dns.html). ---
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [July 1, 2019, 5:11pm UTC](https://discuss.elastic.co/t/ece-url-change/187930/7 "2019-07-01T17:11:24Z")
Excellent, thanks for your quick responses! ---
**Author:** ![crickes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/crickes/32/18009_2.png) [@crickes](https://discuss.elastic.co/u/crickes)\ **Post date:** [July 2, 2019, 1:44pm UTC](https://discuss.elastic.co/t/ece-url-change/187930/8 "2019-07-02T13:44:17Z")
Where does this sit in the development road map? Do you know which release it's targeted for? ---
**Author:** ![zanbel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zanbel/32/20678_2.png) [@zanbel](https://discuss.elastic.co/u/zanbel)\ **Post date:** [July 2, 2019, 2:16pm UTC](https://discuss.elastic.co/t/ece-url-change/187930/9 "2019-07-02T14:16:06Z")
We don't have more information we can share about future roadmap items. ---
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [July 3, 2019, 6:30pm UTC](https://discuss.elastic.co/t/ece-url-change/187930/10 "2019-07-03T18:30:26Z")
So here is the problem I noticed after adding a DNS record and updating the Deployment endpoints field under Platform/Settings: 1. I created a DNS record ([mycompany.com](http://mycompany.com)) for 10.x.x.x 2. I was able to access the ECE URL via the new domain: [https://mycompany.com:12443/](https://mycompany.com:12443/) (it's a DNS lookup, so nothing complicated here) 3. I then changed the 'Deployment endpoints' field under Platform/Settings from [10.x.x.x.ip.es.io](http://10.x.x.x.ip.es.io) to [mycompany.com](http://mycompany.com) and now I can't access Kibana or anything else via a new domain record. 4. I was able to access Kibana via [https://mycompany.com:9243](https://mycompany.com:9243) but I got an error since there was no Cloud ID in the URL: ERROR: {"ok":false,"message":"Unknown cluster."} Question: How do I update "Deployment endpoints" and then be able to access it via Kibana link? --Thanks ---
**Author:** ![daniel\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daniel_a/32/48390_2.png) [@daniel\_a](https://discuss.elastic.co/u/daniel_a)\ **Post date:** [July 8, 2019, 4:29pm UTC](https://discuss.elastic.co/t/ece-url-change/187930/11 "2019-07-08T16:29:30Z")
Easy fix, we added a wild card in GCP (Google Cloud) for the new domain: \*.mycompany.com which points to 10.x.x.x address, and this solved the issue. It worked! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 22, 2019, 4:38pm UTC](https://discuss.elastic.co/t/ece-url-change/187930/12 "2019-07-22T16:38:12Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.