Find connection details

To connect a client application or a third-party tool to Elasticsearch, you need two things: the Elasticsearch endpoint URL, and credentials that authenticate the request. For secure connections, use an API key.

To create an API key, you need the manage_api_key or the manage_own_api_key cluster privilege. If you created the deployment or project, you already have this privilege. If you sign in as a different user, an administrator needs to grant it. In this case, refer to Users and roles.

Copy the Elasticsearch endpoint for your project from the project UI or the Elastic Cloud Console.

  1. In the Elastic Cloud Console, find your project and select Open.
  2. From the Help menu or the project selector in the header, select Connection details.
  3. On the Endpoints tab, copy the Elasticsearch endpoint.
The Connection details panel showing the Elasticsearch endpoint on the Endpoints tab, with the Show Cloud ID toggle and the API key tab
  1. In the Elastic Cloud Console, find your project and select Manage.
  2. Under Application endpoints, select Elasticsearch.
  3. Copy the Direct endpoint value.
The Application endpoints panel in the Elastic Cloud Console, with Elasticsearch expanded to show the Direct endpoint and Direct Azure Private Link endpoint

Azure and AWS also offer an endpoint you can use to connect to the deployment over a private connection. Learn more about private connectivity.

Copy the Elasticsearch endpoint for Elastic Cloud Hosted from the deployment UI or the Elastic Cloud Console.

  1. In the Elastic Cloud Console, find your deployment and select Open.
  2. From the Help menu , select Connection details.
  3. On the Endpoints tab, copy the Elasticsearch endpoint value.
The Connection details panel showing the Elasticsearch endpoint on the Endpoints tab, with the Show Cloud ID toggle and the API key tab
Tip

When the space uses the Elasticsearch solution view, the Getting started page shows the endpoint directly.

  1. In the Elastic Cloud Console, find your deployment and select Manage.
  2. Under Application endpoints, cluster and component IDs, select Elasticsearch.
  3. Copy the Direct endpoint value.
The Application endpoints, cluster and component IDs panel in the Elastic Cloud Console, with Elasticsearch expanded to show the Endpoint, Direct endpoint, and Cluster ID

For Elastic Cloud Enterprise, your endpoint details are in the Connection details panel in Kibana.

  1. Open Kibana for your deployment.
  2. From the Help menu , select Connection details.
  3. Copy the Elasticsearch endpoint from the Endpoints tab.
The Connection details panel showing the Elasticsearch endpoint on the Endpoints tab, with the Show Cloud ID toggle and the API key tab
Tip

When the space uses the Elasticsearch solution view, the Getting started page shows the endpoint directly.

To connect to your Elasticsearch cluster, copy the Elasticsearch endpoint from the deployment page in the Cloud UI.

For a self-managed cluster, one you install and manage, your endpoint takes the form <scheme>://<host>:<port>. Each part comes from your cluster's HTTP settings:

  • Scheme: https when TLS is enabled on the HTTP layer, and http when it isn't. TLS is enabled by default on first startup through automatic security setup, unless the setup is explicitly skipped or disabled, as in the local development quickstart.
  • Host: The address clients use to reach the node, set by http.host or network.host.
  • Port: The HTTP port, set by http.port. It defaults to the range 9200-9300, and a node binds to the first free port in that range.

For example, a single-node cluster from the local development quickstart runs without TLS on the default port, so its endpoint is http://localhost:9200.

If clients reach your cluster through a load balancer, reverse proxy, or ingress, use that address rather than the node address.

The ECK operator automatically creates a service for your Elasticsearch cluster with TLS enabled. Your endpoint URL depends on where your application runs:

  • Inside the same Kubernetes namespace: https://<cluster-name>-es-http:9200
  • In a different namespace: https://<cluster-name>-es-http.<namespace>.svc:9200
  • Outside the Kubernetes cluster: You need to expose the service first. Refer to Access the endpoint for setup steps.

To find your cluster name, run kubectl get svc and look for the service ending in -es-http.

Beats and Logstash can use a Cloud ID instead of the endpoint URL. All other clients and tools use the endpoint.

  1. Open Kibana for your deployment or project.

  2. From the Help menu , select Connection details.

  3. Turn on Show Cloud ID, then copy the value.

    serverless connection details
Tip

To skip Kibana, select Hosted in the Elastic Cloud Console, open your deployment, and copy the Cloud ID from the deployment page.

A personal API key authenticates your client with your own privileges when it sends requests to Elasticsearch. The following steps show you where to create one for your deployment type.

Follow these steps to create an API key for your project.

  1. In the Elastic Cloud Console, find your project and select Open.
  2. From the Help menu , select Connection details.
  3. Select the API key tab.
  4. In the API key name field, enter a name, then select Create API key.
  5. Select an API key format: Encoded for Elasticsearch REST API requests, or Beats or Logstash to configure those products.
  6. Copy the key. It isn't available after you close the panel.

Keys created here expire in 90 days and carry your own privileges. To set an expiration or restrict privileges, select Manage API keys and create the key there instead.

Note

You can also use an Elastic Cloud API key to access Elasticsearch. Use it when the same key needs to access more than one project, or when you use cross-project search.

Follow these steps to create an API key for Elastic Cloud Hosted.

  1. In the Elastic Cloud Console, find your deployment and select Open.
  2. From the Help menu , select Connection details.
  3. Select the API key tab.
  4. In the API key name field, enter a name, then select Create API key.
  5. Select an API key format: Encoded for Elasticsearch REST API requests, or Beats or Logstash to configure those products.
  6. Copy the key. It isn't available after you close the panel.

Keys created here expire in 90 days and carry your own privileges. To set an expiration or restrict privileges, select Manage API keys and create the key there instead.

Follow these steps to create an API key for Elastic Cloud Enterprise.

  1. Open Kibana for your deployment or project.
  2. From the Help menu , select Connection details.
  3. Select the API key tab.
  4. In the API key name field, enter a name, then select Create API key.
  5. Select an API key format: Encoded for Elasticsearch REST API requests, or Beats or Logstash to configure those products.
  6. Copy the key. It isn't available after you close the panel.

Keys created here expire in 90 days and carry your own privileges. To set an expiration or restrict privileges, select Manage API keys and create the key there instead.

Follow these steps to create an API key for a self-managed cluster, one you install and manage.

  1. Go to the API keys management page, using the global search field to find it.
  2. Select Create API key.
  3. Enter a name, then select Create API key.
  4. Copy the key. It isn't available after you leave the page.

Keys created here don't expire unless you add an expiration date.

Follow these steps to create an API key for Elastic Cloud on Kubernetes.

  1. Go to the API keys management page, using the global search field to find it.
  2. Select Create API key.
  3. Enter a name, then select Create API key.
  4. Copy the key. It isn't available after you leave the page.

Keys created here don't expire unless you add an expiration date.

For privileges and expiration options, refer to Elastic API keys.

Verify your endpoint and API key with a request to the Elasticsearch root endpoint.

  1. In a terminal, assign your endpoint and encoded API key to environment variables:

    export ES_URL="https://my-deployment-a1b2c3.es.us-central1.gcp.elastic-cloud.com"
export API_KEY="ZFZRbF9Jb0JDMEoxaVhoR2pSa3Q6dExwdmJSaldRTHFXWEp4TFFlR19Hdw=="

  2. Send the request:

    curl "${ES_URL}" -H "Authorization: ApiKey ${API_KEY}"

A successful response returns your cluster details:

{
  "name" : "instance-0000000000",
  "cluster_name" : "my-deployment",
  "cluster_uuid" : "ws0IbTBUQfigmYAVMztkZQ",
  "version" : { ... },
  "tagline" : "You Know, for Search"
}
Note

If your cluster uses a self-signed certificate, pass your CA certificate with curl --cacert. Refer to Automatic security setup for the certificate location.