You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guide/configuration.asciidoc
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -13,38 +13,38 @@ The options in this section will only be necessary when connecting to Elasticsea
13
13
[discrete]
14
14
==== Verifying certificates
15
15
16
-
The typical route to verify a cluster certificate is via a "CA bundle" which can be specified via the `ca_certs` parameter. If no options are given and the https://github.com/certifi/python-certifi[certifi package] is installed then certifi's CA bundle is used by default.
16
+
The typical route to verify a certificate is via a "CA bundle" which can be specified via the `ca_certs` parameter. If no options are given and the https://github.com/certifi/python-certifi[certifi package] is installed then certifi's CA bundle is used by default.
17
17
18
18
If you have your own CA bundle to use you can configure via the `ca_certs` parameter:
19
19
20
20
[source,python]
21
21
------------------------------------
22
22
es = Elasticsearch(
23
-
cloud_id='deployment-name:ABCD...',
23
+
cloud_id='project-name:ABCD...',
24
24
ca_certs="/path/to/certs.pem"
25
25
)
26
26
------------------------------------
27
27
28
28
If using a generated certificate or certificate with a known fingerprint you can use the `ssl_assert_fingerprint` to specify the fingerprint which tries to match the server's leaf certificate during the TLS handshake. If there is any matching certificate the connection is verified, otherwise a `TlsError` is raised.
29
29
30
-
In Python 3.9 and earlier only the leaf certificate will be verified but in Python 3.10+ private APIs are used to verify any certificate in the certificate chain. This helps when using certificates that are generated on a multi-node cluster.
30
+
In Python 3.9 and earlier only the leaf certificate will be verified but in Python 3.10+ private APIs are used to verify any certificate in the certificate chain.
To disable certificate verification use the `verify_certs=False` parameter. This option should be avoided in production, instead use the other options to verify the clusters' certificate.
42
+
To disable certificate verification use the `verify_certs=False` parameter. This option should be avoided in production, instead use the other options to verify the certificate.
43
43
44
44
[source,python]
45
45
------------------------------------
46
46
es = Elasticsearch(
47
-
cloud_id='deployment-name:ABCD...',
47
+
cloud_id='project-name:ABCD...',
48
48
verify_certs=False
49
49
)
50
50
------------------------------------
@@ -117,7 +117,7 @@ es = Elasticsearch(
117
117
[[timeouts]]
118
118
=== Request timeouts
119
119
120
-
Requests can be configured to timeout if taking too long to be serviced. The `request_timeout` parameter can be passed via the client constructor or the client `.options()` method. When the request times out the node will raise a `ConnectionTimeout` exception which can trigger retries.
120
+
Requests can be configured to timeout if taking too long to be serviced. The `request_timeout` parameter can be passed via the client constructor or the client `.options()` method. When the request times out the project will raise a `ConnectionTimeout` exception which can trigger retries.
121
121
122
122
Setting `request_timeout` to `None` will disable timeouts.
123
123
@@ -305,7 +305,7 @@ es = Elasticsearch(
305
305
[discrete]
306
306
==== HTTP connections
307
307
308
-
The client maintains a pool of HTTP connections to the Elasticsearch Serverless instance to allow for concurrent requests. This value is configurable via the `connections` parameter:
308
+
The client maintains a pool of HTTP connections to the Elasticsearch Serverless project to allow for concurrent requests. This value is configurable via the `connections` parameter:
0 commit comments