- Legacy APM Server Reference:
- Overview
- Get started
- Set up
- How-to guides
- Configure
- Secure
- Monitor
- API
- Explore data in Elasticsearch
- Exported fields
- General APM fields
- APM Error fields
- APM Profile fields
- APM Sourcemap fields
- APM Span fields
- APM Transaction fields
- APM Transaction Metrics fields
- APM Transaction Metrics fields
- Beat fields
- Cloud provider metadata fields
- Docker fields
- ECS fields
- Host fields
- Kubernetes fields
- Process fields
- APM System Metrics fields
- Troubleshoot
- Upgrade
- Release notes
- APM Server version 7.8
- APM Server version 7.7
- APM Server version 7.6
- APM Server version 7.5
- APM Server version 7.4
- APM Server version 7.3
- APM Server version 7.2
- APM Server version 7.1
- APM Server version 7.0
- APM Server version 6.8
- APM Server version 6.7
- APM Server version 6.6
- APM Server version 6.5
- APM Server version 6.4
- APM Server version 6.3
- APM Server version 6.2
- APM Server version 6.1
A newer version is available. For the latest information, see the
current release documentation.
Secure communication with APM Agentsedit
There are two ways to secure the communication between APM Agents and the APM Server. Both options can be enabled at the same time, allowing Elastic APM agents to chose whichever mechanism they support.
As soon as secure communication is enabled, requests without a valid token or API key will be denied by APM Server. As RUM endpoints cannot be secured, they are exempt from this rule.
Was this helpful?
Thank you for your feedback.