Change endpoint URLs
editChange endpoint URLs
editFor applications without SSL or HTTPS protocol support, you can use a local endpoint with the HTTP protocol, which in turn connects to your Elasticsearch cluster or to Kibana either using the HTTP or the HTTPS protocol.
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 https://2882c82e54d4361.us-west-5.aws.found.io:9243
To find your endpoints, select a deployment review the information on the Elasticsearch and Kibana pages.
To change endpoints in the Cloud UI:
- Log into the Cloud UI.
- From the Platform menu, select Settings.
- Specify the deployment domain name value for your cluster and Kibana endpoints.
- Select Update Deployment endpoints. The new endpoint becomes effective immediately.
If you install Elastic Cloud Enterprise on AWS, you likely need to modify the cluster endpoint. To learn more, check Endpoint 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 Search cluster 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 in Manage security certificates. For test only, clients can be configured with hostname verification disabled until the new certificate is uploaded.