APM agent authorizationedit

Agent authorization APM Server configuration options.

Example config file:

  host: "localhost:8200"
    enabled: true

    hosts: ElasticsearchAddress:9200

max_procs: 4

API key authentication optionsedit

These settings apply to API key communication between the APM Server and APM Agents.

These settings are different from the API key settings used for Elasticsearch output and monitoring.

API key for agent authenticationedit

Enable API key authorization by setting enabled to true. By default, enabled is set to false, and API key support is disabled. (bool)

APM Server binary



API key for agent authentication

Not using Elastic APM agents? When enabled, third-party APM agents must include a valid API key in the following format: Authorization: ApiKey <token>. The key must be the base64 encoded representation of the API key’s id:name.

API key limitedit

Each unique API key triggers one request to Elasticsearch. This setting restricts the number of unique API keys are allowed per minute. The minimum value for this setting should be the number of API keys configured in your monitored services. The default limit is 100. (int)

APM Server binary



Number of keys

Secret tokenedit

Authorization token for sending APM data. The same token must also be set in each APM agent. This token is not used for RUM endpoints. (text)

APM Server binary



Secret token

auth.api_key.elasticsearch.* configuration optionsedit


API keys are fetched from Elasticsearch. This configuration needs to point to a secured Elasticsearch cluster that is able to serve API key requests.


The name of the protocol Elasticsearch is reachable on. The options are: http or https. The default is http. If nothing is configured, configuration settings from the output section will be reused.


An optional HTTP path prefix that is prepended to the HTTP API calls. If nothing is configured, configuration settings from the output section will be reused.


The URL of the proxy to use when connecting to the Elasticsearch servers. The value may be either a complete URL or a "host[:port]", in which case the "http"scheme is assumed. If nothing is configured, configuration settings from the output section will be reused.


The HTTP request timeout in seconds for the Elasticsearch request. If nothing is configured, configuration settings from the output section will be reused.

auth.api_key.elasticsearch.ssl.* configuration optionsedit

SSL is off by default. Set elasticsearch.protocol to https if you want to enable https.


Enable custom SSL settings. Set to false to ignore custom SSL settings for secure communication.


Configure SSL verification mode. If none is configured, all server hosts and certificates will be accepted. In this mode, SSL based connections are susceptible to man-in-the-middle attacks. Use only for testing. Default is full.


List of supported/valid TLS versions. By default, all TLS versions from 1.0 to 1.2 are enabled.


List of root certificates for HTTPS server verifications.


The path to the certificate for SSL client authentication.


The client certificate key used for client authentication. This option is required if certificate is specified.


An optional passphrase used to decrypt an encrypted key stored in the configured key file.


The list of cipher suites to use. The first entry has the highest priority. If this option is omitted, the Go crypto library’s default suites are used (recommended).


The list of curve types for ECDHE (Elliptic Curve Diffie-Hellman ephemeral key exchange).


Configure what types of renegotiation are supported. Valid options are never, once, and freely. Default is never.

  • never - Disables renegotiation.
  • once - Allows a remote server to request renegotiation once per connection.
  • freely - Allows a remote server to repeatedly request renegotiation.