[New search IA] Adds Set up section

deploy-manage/deploy/elastic-cloud/_snippets/find-endpoint-serverless-console.md

@@ -1,12 +1,11 @@
-1. In the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), select **Serverless**.
-2. Find your project and select **Manage**.
-3. Under **Application endpoints, cluster and component IDs**, select **{{es}}**.
-4. Copy the **Endpoint** value.
+1. In the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), find your project and select **Manage**.
+2. Under **Application endpoints**, select **{{es}}**.
+3. Copy the **Direct endpoint** value.
 
     :::{image} /solutions/images/cloud-console-serverless-endpoint.png
-    :alt: The Elasticsearch panel on a Serverless project page in the Elastic Cloud Console, showing the Endpoint and AWS PrivateLink endpoint values with copy buttons
+    :alt: The Application endpoints panel in the {{ecloud}} Console, with {{es}} expanded to show the Direct endpoint and Direct Azure Private Link endpoint
     :screenshot:
     :width: 50%
     :::
 
-If your project runs on AWS, the panel also lists an **AWS PrivateLink endpoint**. Use it only when you connect through AWS PrivateLink. To learn more, refer to [](/deploy-manage/security/private-connectivity-aws.md).
+Azure and {{aws}} also offer an endpoint you can use to connect to the deployment over a private connection. [Learn more about private connectivity](/deploy-manage/security/private-connectivity.md).

solutions/elasticsearch-solution-project/_snippets/create-an-api-key.md

@@ -0,0 +1,83 @@
+<!--
+This snippet is in use in the following locations:
+- solutions/elasticsearch-solution-project/search-connection-details.md
+- solutions/search/set-up/api-key-and-endpoints.md
+-->
+
+A personal API key authenticates your client with your own privileges when it sends requests to {{es}}. The following steps show you where to create one for your deployment type.
+
+:::::{applies-switch}
+
+::::{applies-item} serverless: ga
+
+Follow these steps to create an API key for your project.
+
+1. In the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), find your project and select **Open**.
+2. From the **Help menu** {icon}`question`, 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 {{es}} REST API requests, or **{{beats}}** or **{{ls}}** 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 [{{ecloud}} API key](/deploy-manage/api-keys/elastic-cloud-api-keys.md) to access {{es}}. Use it when the same key needs to access more than one project, or when you use [{{cps}}](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#manage-user-and-api-key-access).
+:::
+::::
+
+::::{applies-item} ech: ga
+
+Follow these steps to create an API key for {{ech}}.
+
+1. In the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), find your deployment and select **Open**.
+2. From the **Help menu** {icon}`question`, 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 {{es}} REST API requests, or **{{beats}}** or **{{ls}}** 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.
+::::
+
+::::{applies-item} ece: ga
+
+Follow these steps to create an API key for {{ece}}.
+
+1. Open {{kib}} for your deployment or project.
+2. From the **Help menu** {icon}`question`, 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 {{es}} REST API requests, or **{{beats}}** or **{{ls}}** 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.
+::::
+
+::::{applies-item} {"deployment": {"self": "ga"}}
+
+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](/explore-analyze/find-and-organize/find-apps-and-objects.md) 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.
+::::
+
+::::{applies-item} {"deployment": {"eck": "ga"}}
+
+Follow these steps to create an API key for {{eck}}.
+
+1. Go to the **API keys** management page, using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) 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 [](/deploy-manage/api-keys.md).

solutions/elasticsearch-solution-project/_snippets/find-elasticsearch-endpoint.md

@@ -0,0 +1,145 @@
+<!--
+This snippet is in use in the following locations:
+- solutions/elasticsearch-solution-project/search-connection-details.md
+- solutions/search/set-up/api-key-and-endpoints.md
+-->
+
+:::::::{applies-switch}
+
+::::::{applies-item} serverless: ga
+Copy the {{es}} endpoint for your project from the project UI or the {{ecloud}} Console.
+
+:::::{tab-set}
+
+::::{tab-item} Project UI
+
+1. In the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), find your project and select **Open**.
+2. From the **Help menu** {icon}`question` or the project selector in the header, select **Connection details**.
+3. On the **Endpoints** tab, copy the **{{es}} endpoint**.
+
+:::{image} /solutions/images/kibana-connection-details-endpoints.png
+:alt: The Connection details panel showing the {{es}} endpoint on the Endpoints tab, with the Show Cloud ID toggle and the API key tab
+:screenshot:
+:width: 50%
+:::
+
+::::
+
+::::{tab-item} {{ecloud}} Console
+
+1. In the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), find your project and select **Manage**.
+2. Under **Application endpoints**, select **{{es}}**.
+3. Copy the **Direct endpoint** value.
+
+:::{image} /solutions/images/cloud-console-serverless-endpoint.png
+:alt: The Application endpoints panel in the {{ecloud}} Console, with {{es}} expanded to show the Direct endpoint and Direct Azure Private Link endpoint
+:screenshot:
+:width: 50%
+:::
+
+Azure and AWS also offer an endpoint you can use to connect to the deployment over a private connection. [Learn more about private connectivity](/deploy-manage/security/private-connectivity.md).
+
+::::
+
+:::::
+
+::::::
+
+::::::{applies-item} ech: ga
+Copy the {{es}} endpoint for {{ech}} from the deployment UI or the {{ecloud}} Console.
+
+:::::{tab-set}
+
+::::{tab-item} {{kib}} UI
+
+1. In the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), find your deployment and select **Open**.
+2. From the **Help menu** {icon}`question`, select **Connection details**.
+3. On the **Endpoints** tab, copy the **{{es}} endpoint** value.
+
+:::{image} /solutions/images/kibana-connection-details-endpoints.png
+:alt: The Connection details panel showing the {{es}} endpoint on the Endpoints tab, with the Show Cloud ID toggle and the API key tab
+:screenshot:
+:width: 50%
+:::
+
+:::{tip}
+When the space uses the **{{es}}** solution view, the **Getting started** page shows the endpoint directly.
+:::
+
+::::
+
+::::{tab-item} {{ecloud}} Console
+
+1. In the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), find your deployment and select **Manage**.
+2. Under **Application endpoints, cluster and component IDs**, select **{{es}}**.
+3. Copy the **Direct endpoint** value.
+
+:::{image} /solutions/images/cloud-console-hosted-endpoint.png
+:alt: The Application endpoints, cluster and component IDs panel in the {{ecloud}} Console, with {{es}} expanded to show the Endpoint, Direct endpoint, and Cluster ID
+:screenshot:
+:width: 50%
+:::
+
+::::
+
+:::::
+
+::::::
+
+::::::{applies-item} ece: ga
+
+:::::{tab-set}
+
+::::{tab-item} {{kib}}
+
+For {{ece}}, your endpoint details are in the **Connection details** panel in {{kib}}.
+
+1. Open {{kib}} for your deployment.
+2. From the **Help menu** {icon}`question`, select **Connection details**.
+3. Copy the **{{es}} endpoint** from the **Endpoints** tab.
+
+:::{image} /solutions/images/kibana-connection-details-endpoints.png
+:alt: The Connection details panel showing the {{es}} endpoint on the Endpoints tab, with the Show Cloud ID toggle and the API key tab
+:screenshot:
+:width: 50%
+:::
+
+:::{tip}
+When the space uses the **{{es}}** solution view, the **Getting started** page shows the endpoint directly.
+:::
+
+::::
+
+::::{tab-item} Cloud UI
+
+To connect to your {{es}} cluster, copy the **{{es}} endpoint** from the deployment page in the [Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
+
+::::
+
+:::::
+
+::::::
+
+::::{applies-item} {"deployment": {"self": "ga"}}
+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](/deploy-manage/security/self-auto-setup.md), unless the setup is [explicitly skipped](/deploy-manage/security/self-auto-setup.md#stack-skip-auto-configuration) or disabled, as in the local development quickstart.
+* **Host**: The address clients use to reach the node, set by [`http.host` or `network.host`](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md).
+* **Port**: The HTTP port, set by [`http.port`](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md). 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](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md) 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.
+::::
+
+::::{applies-item} {"deployment": {"eck": "ga"}}
+The ECK operator automatically creates a service for your {{es}} 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](/deploy-manage/deploy/cloud-on-k8s/accessing-services.md#k8s-request-elasticsearch-endpoint) for setup steps.
+
+To find your cluster name, run `kubectl get svc` and look for the service ending in `-es-http`.
+::::
+
+:::::::

solutions/elasticsearch-solution-project/search-connection-details.md

@@ -1,6 +1,6 @@
 ---
 navigation_title: Find connection details
-description: Find your Elasticsearch endpoint and create an API key so that client applications and tools can connect to your cluster or project.
+description: Find your {{es}} endpoint and create an API key so that client applications and tools can connect to your cluster or project.
 mapped_pages:
   - https://www.elastic.co/guide/en/kibana/current/search-space-connection-details.html
 applies_to:
@@ -18,88 +18,14 @@ To connect a client application or a third-party tool to {{es}}, you need two th
 
 ## Before you begin [before-you-begin]
 
-To create an API key, you need the `manage_api_key` or the `manage_own_api_key` cluster privilege.
+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 [](/deploy-manage/users-roles.md).
 
 ## Find your {{es}} endpoint [find-endpoint-cloud-self-managed]
 
-:::::{applies-switch}
-
-::::{applies-item} serverless: ga
-Your endpoint details are on your project's page in the {{ecloud}} Console.
-
-:::{include} /deploy-manage/deploy/elastic-cloud/_snippets/find-endpoint-serverless-console.md
-:::
-
-:::{tip}
-You can also find your endpoint details in {{kib}}. From the **Help menu** {icon}`question` or the project selector in the header, select **Connection details**, then copy the **{{es}} endpoint** from the **Endpoints** tab.
-:::
-::::
-
-::::{applies-item} ech: ga
-Your endpoint details are on your deployment's page in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
-
-1. In the {{ecloud}} Console, select **Hosted**.
-2. Select your deployment.
-3. Under **Application endpoints, cluster and component IDs**, select **{{es}}**.
-4. Copy the **Endpoint** value.
-
-    :::{image} /solutions/images/cloud-console-hosted-endpoint.png
-    :alt: The Elasticsearch panel on a hosted deployment page in the Elastic Cloud Console, showing the Endpoint value with a copy button
-    :screenshot:
-    :width: 50%
-    :::
-
-:::{tip}
-You can also find your endpoint details in {{kib}}. From the **Help menu** {icon}`question`, select **Connection details**, then copy the **{{es}} endpoint** from the **Endpoints** tab.
-:::
-::::
-
-::::{applies-item} ece: ga
-Your endpoint details are in the **Connection details** panel in {{kib}}.
-
-1. Open {{kib}} for your deployment.
-2. From the **Help menu** {icon}`question`, select **Connection details**.
-3. Copy the **{{es}} endpoint** from the **Endpoints** tab.
-
-:::{image} /solutions/images/kibana-connection-details-endpoints.png
-:alt: The Connection details panel showing the Elasticsearch endpoint on the Endpoints tab, with the Show Cloud ID toggle and the API key tab
-:screenshot:
-:width: 50%
-:::
-
-:::{tip}
-When the space uses the **{{es}}** solution view, the **Getting started** page shows the endpoint directly.
+:::{include} /solutions/elasticsearch-solution-project/_snippets/find-elasticsearch-endpoint.md
 :::
 
-::::
-
-::::{applies-item} {"deployment": {"self": "ga"}}
-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. [Automatic security setup](/deploy-manage/security/self-auto-setup.md) enables TLS on a new archive or package installation.
-* **Host**: The address clients use to reach the node, set by [`http.host` or `network.host`](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md).
-* **Port**: The HTTP port, set by [`http.port`](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md). 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](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md) 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.
-::::
-
-::::{applies-item} {"deployment": {"eck": "ga"}}
-The {{eck}} operator creates a `ClusterIP` service named `<cluster-name>-es-http` on port `9200`, with TLS enabled by default.
-
-From inside the Kubernetes cluster, your endpoint is `https://<cluster-name>-es-http:9200` in the same namespace, or `https://<cluster-name>-es-http.<namespace>.svc:9200` from another namespace. List your services to confirm the name:
-
-```sh
-kubectl get svc
-```
-
-To reach the cluster from outside, expose the service and use its external address. Refer to [Access the endpoint](/deploy-manage/deploy/cloud-on-k8s/accessing-services.md#k8s-request-elasticsearch-endpoint) for both cases, including how to retrieve the certificate authority (CA) certificate.
-::::
-
-:::::
-
-### Find your Cloud ID [find-cloud-id-cloud-self-managed]
+## Find your Cloud ID [find-cloud-id-cloud-self-managed]
 
 ```{applies_to}
 deployment:
@@ -127,32 +53,8 @@ To skip {{kib}}, select **Hosted** in the {{ecloud}} Console, open your deployme
 
 ## Create an API key [create-an-api-key-cloud-self-managed]
 
-:::::{applies-switch}
-
-::::{applies-item} { "deployment": { "ech": "ga", "ece": "ga" }, "serverless": "ga" }
-
-1. Open {{kib}} for your deployment or project.
-2. From the **Help menu** {icon}`question`, 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 {{es}} 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.
-::::
-
-::::{applies-item} {"deployment": {"eck": "ga", "self": "ga"}}
-1. Go to the **API keys** management page, using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) 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 key types, privileges, and expiration options, refer to [](/deploy-manage/api-keys.md).
+:::{include} /solutions/elasticsearch-solution-project/_snippets/create-an-api-key.md
+:::
 
 ## Test your connection [elasticsearch-get-started-test-connection]
 
@@ -196,6 +98,6 @@ If your cluster uses a self-signed certificate, pass your CA certificate with `c
 
 ## Related pages
 
-* [Configure Beats and {{ls}} with a Cloud ID](/deploy-manage/deploy/elastic-cloud/find-cloud-id.md)
+* [Configure {{beats}} and {{ls}} with a Cloud ID](/deploy-manage/deploy/elastic-cloud/find-cloud-id.md)
 * [Connect to {{es}} on {{ece}}](/deploy-manage/deploy/cloud-enterprise/connect-elasticsearch.md)
 * [Securing HTTP client applications](/deploy-manage/security/httprest-clients-security.md)