Find your Serverless project connection details

Note

This page is for Elastic Cloud Serverless projects. If you're using an Elastic Cloud Hosted deployment, refer to Find your Cloud ID.

When you connect clients and tools to an Elastic Cloud Serverless project, these are the main connection details you'll work with:

Elasticsearch endpoint
The HTTPS URL you use to send requests to your project. Most clients, SDKs, and integrations connect with this URL plus an API key.
API key
Authenticates the client to your project. Serverless does not support username and password authentication for these connections.
Cloud ID
A unique, encoded string that represents your project's Elasticsearch endpoint (and, where applicable, Kibana endpoint) in a compact form. Compatible clients can use it instead of configuring host URLs individually: the client resolves those endpoints from the Cloud ID.

Find your Elasticsearch endpoint

You can copy your endpoint from the Elastic Cloud Console, or from Kibana. Use whichever fits your workflow: the Console route doesn't require you to open Kibana.

In Elasticsearch Serverless projects, the Get started with Elasticsearch page also shows the endpoint directly.

From the Elastic Cloud Console

  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.

Other endpoints in this panel

The Application endpoints, cluster and component IDs area also lists endpoints for other applications, such as Kibana and, depending on the project type, Fleet or OpenTelemetry (OTLP), along with your project ID and component IDs. To connect clients and tools to Elasticsearch, use the Elasticsearch endpoint.

From Kibana

  1. Open the Connection details panel in one of these ways:

    • Select the Help menu , and then select Connection details.
    • Select the project selector in the header, and then select Connection details.

  2. 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

Find your Cloud ID

The Cloud ID is available in Kibana only. You need it only for Beats and Logstash, which can use it in place of the endpoint URL. All other clients and tools use the endpoint.

  1. In Kibana, open the Connection details panel from the Help menu or the project selector in the header.
  2. Turn on Show Cloud ID, then copy the value.

Create an API key

You can create an API key in the API key tab of the Connection details panel.

Alternatively, you can also create an API key from your project's API keys page, which you can access from the navigation menu or with the global search field.

For detailed steps, including how to restrict a key's privileges and how to update or delete keys, refer to Serverless project API keys.

Elastic Cloud API keys

Keys created in your project work with that project only. If you want one key to work across several projects, or to manage keys centrally, create an Elastic Cloud API key in the Elastic Cloud Console instead.

Elastic Cloud API keys manage your organization, deployments, and projects. To also use one in place of a project API key, grant it Elasticsearch and Kibana API access for the relevant projects.

Next steps

After you have your project's connection details, send a test request to confirm that your endpoint and API key work, then use them to configure a client or data shipper. Explore these pages: