From cb23133416821587693ecd0be66d5a9e406bcf0d Mon Sep 17 00:00:00 2001 From: Som <111349830+someshwaranM@users.noreply.github.com> Date: Mon, 21 Apr 2025 19:38:03 +0700 Subject: [PATCH 1/2] Update secure-connections.md - spacing issue. --- reference/fleet/secure-connections.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/fleet/secure-connections.md b/reference/fleet/secure-connections.md index a82efe5337..30b3ff56cd 100644 --- a/reference/fleet/secure-connections.md +++ b/reference/fleet/secure-connections.md @@ -90,7 +90,7 @@ For the steps in this section, imagine you have the following files: | | | | --- | --- | -| `ca.crt` | The CA certificate to use to connect to {{fleet-server}}. This is theCA used to [generate a certificate and key](#generate-fleet-server-certs)for {{fleet-server}}. | +| `ca.crt` | The CA certificate to use to connect to {{fleet-server}}. This is the CA used to [generate a certificate and key](#generate-fleet-server-certs) for {{fleet-server}}. | | `fleet-server.crt` | The certificate you generated for {{fleet-server}}. | | `fleet-server.key` | The private key you generated for {{fleet-server}}.
If the `fleet-server.key` file is encrypted with a passphrase, the passphrase will need to be specified through a file. | | `elasticsearch-ca.crt` | The CA certificate to use to connect to {{es}}. This is the CA used to generatecerts for {{es}} (see [Prerequisites](#prereqs)).
Note that the CA certificate’s SHA-256 fingerprint (hash) may be used instead of the `elasticsearch-ca.crt` file for securing connections to {{es}}. | From 86e7923fe7c3d27d9a9b8ae3a8abf45302f730aa Mon Sep 17 00:00:00 2001 From: George Wallace Date: Mon, 21 Apr 2025 08:57:45 -0600 Subject: [PATCH 2/2] Update secure-connections.md Making changes based on co-pilot review --- reference/fleet/secure-connections.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/fleet/secure-connections.md b/reference/fleet/secure-connections.md index 30b3ff56cd..94dc4cb2c7 100644 --- a/reference/fleet/secure-connections.md +++ b/reference/fleet/secure-connections.md @@ -93,7 +93,7 @@ For the steps in this section, imagine you have the following files: | `ca.crt` | The CA certificate to use to connect to {{fleet-server}}. This is the CA used to [generate a certificate and key](#generate-fleet-server-certs) for {{fleet-server}}. | | `fleet-server.crt` | The certificate you generated for {{fleet-server}}. | | `fleet-server.key` | The private key you generated for {{fleet-server}}.
If the `fleet-server.key` file is encrypted with a passphrase, the passphrase will need to be specified through a file. | -| `elasticsearch-ca.crt` | The CA certificate to use to connect to {{es}}. This is the CA used to generatecerts for {{es}} (see [Prerequisites](#prereqs)).
Note that the CA certificate’s SHA-256 fingerprint (hash) may be used instead of the `elasticsearch-ca.crt` file for securing connections to {{es}}. | +| `elasticsearch-ca.crt` | The CA certificate to use to connect to {{es}}. This is the CA used to generate certs for {{es}} (see [Prerequisites](#prereqs)).
Note that the CA certificate’s SHA-256 fingerprint (hash) may be used instead of the `elasticsearch-ca.crt` file for securing connections to {{es}}. | To encrypt traffic between {{agent}}s, {{fleet-server}}, and {{es}}: