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
* **Profiler runtime instrumentation**: The agent supports auto instrumentation without any code change and without any recompilation of your projects. See [Profiler auto instrumentation](asciidocalypse://docs/apm-agent-dotnet/docs/reference/setup-auto-instrumentation.md).
133
-
* **NuGet packages**: The agent ships as a set of [NuGet packages](asciidocalypse://docs/apm-agent-dotnet/docs/reference/nuget-packages.md) available on [nuget.org](https://nuget.org). You can add the Agent and specific instrumentations to a .NET application by referencing one or more of these packages and following the package documentation.
134
-
* **Host startup hook**: On .NETCore3.0+ or .NET5+, the agent supports auto instrumentation without any code change and without any recompilation of your projects. See [Zero code change setup on .NETCore](asciidocalypse://docs/apm-agent-dotnet/docs/reference/setup-dotnet-net-core.md) for more details.
132
+
* **Profiler runtime instrumentation**: The agent supports auto instrumentation without any code change and without any recompilation of your projects. See [Profiler auto instrumentation](apm-agent-dotnet://reference/setup-auto-instrumentation.md).
133
+
* **NuGet packages**: The agent ships as a set of [NuGet packages](apm-agent-dotnet://reference/nuget-packages.md) available on [nuget.org](https://nuget.org). You can add the Agent and specific instrumentations to a .NET application by referencing one or more of these packages and following the package documentation.
134
+
* **Host startup hook**: On .NETCore3.0+ or .NET5+, the agent supports auto instrumentation without any code change and without any recompilation of your projects. See [Zero code change setup on .NETCore](apm-agent-dotnet://reference/setup-dotnet-net-core.md) for more details.
Copy file name to clipboardExpand all lines: solutions/observability/apps/apm-agent-tls-communication.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,10 +10,10 @@ TLS is disabled by default. When TLS is enabled for APM Server inbound communica
10
10
When TLS is enabled, a certificate and corresponding private key are required. The certificate and private key can either be issued by a trusted certificate authority (CA) or be [self-signed](#apm-agent-self-sign).
11
11
12
12
13
-
## Use a self-signed certificate [apm-agent-self-sign]
13
+
## Use a self-signed certificate [apm-agent-self-sign]
14
14
15
15
16
-
### Step 1: Create a self-signed certificate [apm-agent-self-sign-1]
16
+
### Step 1: Create a self-signed certificate [apm-agent-self-sign-1]
17
17
18
18
The {{es}} distribution offers the `certutil` tool for the creation of self-signed certificates:
19
19
@@ -23,7 +23,7 @@ The {{es}} distribution offers the `certutil` tool for the creation of self-sign
23
23
4. Extract the certificate and key from the resulted zip archive.
24
24
25
25
26
-
### Step 2: Configure the APM Server [apm-agent-self-sign-2]
26
+
### Step 2: Configure the APM Server [apm-agent-self-sign-2]
27
27
28
28
Enable TLS and configure the APM Server to point to the extracted certificate and key:
A full list of configuration options is available in [SSL/TLS input settings](ssltls-input-settings.md).
46
46
47
-
::::{tip}
47
+
::::{tip}
48
48
If APM agents are authenticating themselves using a certificate that cannot be authenticated through known CAs (e.g. self signed certificates), use the `ssl.certificate_authorities` to set a custom CA. This will automatically modify the `ssl.client_authentication` configuration to require authentication.
When the APM server uses a certificate that is not chained to a publicly-trusted certificate (e.g. self-signed), additional configuration is required in the {{apm-agent}}:
57
57
58
58
* **Go agent**: certificate pinning through [`ELASTIC_APM_SERVER_CERT`](asciidocalypse://docs/apm-agent-go/docs/reference/configuration.md#config-server-cert)
59
59
* **Python agent**: certificate pinning through [`server_cert`](asciidocalypse://docs/apm-agent-python/docs/reference/configuration.md#config-server-cert)
60
60
* **Ruby agent**: certificate pinning through [`server_ca_cert`](asciidocalypse://docs/apm-agent-ruby/docs/reference/configuration.md#config-ssl-ca-cert)
* **Node.js agent**: custom CA setting through [`serverCaCertFile`](asciidocalypse://docs/apm-agent-nodejs/docs/reference/configuration.md#server-ca-cert-file)
63
63
* **Java agent**: adding the certificate to the JVM `trustStore`. See [APM Server authentication](asciidocalypse://docs/apm-agent-java/docs/reference/ssl-configuration.md#ssl-server-authentication) for more details.
64
64
65
65
We do not recommend disabling {{apm-agent}} verification of the server’s certificate, but it is possible:
APM Server does not require agents to provide a certificate for authentication, and there is no dedicated support for SSL/TLS client certificate authentication in Elastic’s backend agents.
Copy file name to clipboardExpand all lines: solutions/observability/apps/apm-server-binary.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -396,14 +396,14 @@ Refer to [Manual setup with `-javaagent` flag](asciidocalypse://docs/apm-agent-j
396
396
397
397
The .NET agent can be added to an application in a few different ways:
398
398
399
-
***Profiler runtime instrumentation**: The agent supports auto instrumentation without any code change and without any recompilation of your projects. See [Profiler auto instrumentation](asciidocalypse://docs/apm-agent-dotnet/docs/reference/setup-auto-instrumentation.md).
400
-
***NuGet packages**: The agent ships as a set of [NuGet packages](asciidocalypse://docs/apm-agent-dotnet/docs/reference/nuget-packages.md) available on [nuget.org](https://nuget.org). You can add the Agent and specific instrumentations to a .NET application by referencing one or more of these packages and following the package documentation.
401
-
***Host startup hook**: On .NET Core 3.0+ or .NET 5+, the agent supports auto instrumentation without any code change and without any recompilation of your projects. See [Zero code change setup on .NET Core](asciidocalypse://docs/apm-agent-dotnet/docs/reference/setup-dotnet-net-core.md) for more details.
399
+
***Profiler runtime instrumentation**: The agent supports auto instrumentation without any code change and without any recompilation of your projects. See [Profiler auto instrumentation](apm-agent-dotnet://reference/setup-auto-instrumentation.md).
400
+
***NuGet packages**: The agent ships as a set of [NuGet packages](apm-agent-dotnet://reference/nuget-packages.md) available on [nuget.org](https://nuget.org). You can add the Agent and specific instrumentations to a .NET application by referencing one or more of these packages and following the package documentation.
401
+
***Host startup hook**: On .NET Core 3.0+ or .NET 5+, the agent supports auto instrumentation without any code change and without any recompilation of your projects. See [Zero code change setup on .NET Core](apm-agent-dotnet://reference/setup-dotnet-net-core.md) for more details.
0 commit comments