- Legacy APM Server Reference:
- Overview
- Getting Started With APM Server
- Setting up APM Server
- Upgrading APM Server
- Configuring APM Server
- General configuration options
- Configure the output
- Parse data using ingest node pipelines
- SSL/TLS settings
- Load the Elasticsearch index template
- Index lifecycle management (ILM)
- Configure logging
- Configure the Kibana endpoint
- Set up Real User Monitoring (RUM) support
- Use environment variables in the configuration
- Configure project paths
- Securing APM Server
- Monitoring APM Server
- Real User Monitoring (RUM)
- Tune Data Ingestion
- Storage Management
- Intake API
- Exploring data in Elasticsearch
- Exported fields
- Troubleshooting
- Release notes
Configure APM Server to use X-Pack securityedit
If you want APM Server to connect to a cluster that has X-Pack security enabled, there are extra configuration steps:
-
Grant users access to secured resources.
You can use role-based access control to grant APM Server users access to secured resources.
-
Configure authentication credentials.
To interact with a secured cluster, APM Server must either provide basic authentication credentials or present a client certificate.
-
Configure APM Server to use encrypted connections.
If encryption is enabled on the cluster, you need to enable HTTPS in the APM Server configuration.
-
Set the password for the built-in monitoring user.
APM Server uses the
apm_systemuser to send monitoring data to Elasticsearch. If you plan to monitor APM Server in Kibana and have not yet set up the password, set it up now.
For more information about X-Pack security, see Securing the Elastic Stack.