It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.
The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
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 CNAME value for your cluster and Kibana endpoints.
- Click 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, see Endpoint URLs Inaccessible on AWS.