Skip to content

Commit 407ca69

Browse files
authored
Update getting-started.asciidoc
The connection should be using the cloud id and API key, not the cloud endpoint. The image unfortunately will need to be updated to as it obfuscates the cloud id and highlights the endpoint copy. This would be consistent with our docs here https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/connecting.html#cloud-deployment Which states always use the cloud id, for our Elastic Cloud Hosted deployments to connect.
1 parent 36e93ee commit 407ca69

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

docs/getting-started.asciidoc

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,16 +27,17 @@ Refer to the <<installation>> page to learn more.
2727
=== Connecting
2828

2929
You can connect to the Elastic Cloud using an API key and the Elasticsearch
30-
endpoint.
30+
cloud id.
3131

3232
[source,net]
3333
----
3434
var client = new ElasticsearchClient("<CLOUD_ID>", new ApiKey("<API_KEY>"));
3535
----
3636

37-
Your Elasticsearch endpoint can be found on the **My deployment** page of your
37+
Your Elasticsearch cloud id can be found on the **My deployment** page of your
3838
deployment:
3939

40+
****** REPLACE IMAGE WITH CORRECTED ONE*****
4041
image::images/es-endpoint.jpg[alt="Finding Elasticsearch endpoint",align="center"]
4142

4243
You can generate an API key on the **Management** page under Security.
@@ -158,4 +159,4 @@ var response = await client.Indices.DeleteAsync("my_index");
158159
== Further reading
159160

160161
* Refer to the <<recommendations>> page to learn more about how to use the
161-
client the most efficiently.
162+
client the most efficiently.

0 commit comments

Comments
 (0)