Change endpoint URLs
Elasticsearch and Kibana endpoint URLs are constructed using theCLUSTER_ID of the component (Elasticsearch or Kibana), and the domain name (CNAME) configured in theDeployment Endpoints section of thePlatform > Settings UI.
By default, the deploymentsCNAME is set toLOCAL_HOST_IP.ip.es.io, whereLOCAL_HOST_IP is the IP address of the first installed ECE host. This results in the following default endpoint URLs:
http://<CLUSTER_ID.LOCAL_HOST_IP>.ip.es.io:9200https://<CLUSTER_ID.LOCAL_HOST_IP>.ip.es.io:9243For security reasons, it is recommended to useHTTPS (9243) whenever possible.
To change endpoints in the Cloud UI:
- Log into the Cloud UI.
- From thePlatform menu, selectSettings.
- Specify the deployment domain name (
CNAME) value for your cluster and Kibana endpoints. - SelectUpdate Deployment endpoints. The new endpoint becomes effective immediately.
To find your deployment endpoints, select a deployment and review the information on theElasticsearch andKibana pages.
If you install Elastic Cloud Enterprise on AWS, you likely need to modify the cluster endpoint. To learn more, checkEndpoint URLs Inaccessible on AWS.
If you have an App Search instance, after specifying a new deployment domain name value you need to reapply the App Searchcluster configuration, either with or without any changes.
The built-in Proxy Certificate only validates against the default endpoint format described on this page. Once you change it, it is necessary to upload a new Proxy Certificate as described inManage security certificates. For test only, clients can be configured with hostname verification disabled until the new certificate is uploaded.
If you do not use wildcard certificates, you must configure SAN entries for each component of the deployment (for example, Elasticsearch or Kibana) and repeat this process for every deployment. ReviewWildcard DNS record and certificates for more guidance.