- Observability: other versions:
- Get started
- What is Elastic Observability?
- What’s new in 8.17
- Quickstart: Monitor hosts with Elastic Agent
- Quickstart: Monitor your Kubernetes cluster with Elastic Agent
- Quickstart: Monitor hosts with OpenTelemetry
- Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)
- Quickstart: Collect data with AWS Firehose
- Add data from Splunk
- Applications and services
- Application performance monitoring (APM)
- Get started
- Learn about data types
- Collect application data
- View and analyze data
- Act on data
- Use APM securely
- Manage storage
- Configure APM Server
- Monitor APM Server
- APM APIs
- Troubleshooting
- Upgrade
- Release notes
- Known issues
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Multi-factor Authentication
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Real user monitoring
- Uptime monitoring (deprecated)
- Tutorial: Monitor a Java application
- Application performance monitoring (APM)
- CI/CD
- Cloud
- Infrastructure and hosts
- Logs
- Troubleshooting
- Incident management
- Data set quality
- Observability AI Assistant
- Reference
Configure the output for Elasticsearch Service on Elastic Cloud
editConfigure the output for Elasticsearch Service on Elastic Cloud
editThis page refers to using a separate instance of APM Server with an existing Elasticsearch Service deployment. If you want to use APM on Elasticsearch Service, see: Create your deployment and Add APM user settings.
APM Server comes with two settings that simplify the output configuration when used together with Elasticsearch Service. When defined, these setting overwrite settings from other parts in the configuration.
Example:
cloud.id: "staging:dXMtZWFzdC0xLmF3cy5mb3VuZC5pbyRjZWM2ZjI2MWE3NGJmMjRjZTMzYmI4ODExYjg0Mjk0ZiRjNmMyY2E2ZDA0MjI0OWFmMGNjN2Q3YTllOTYyNTc0Mw==" cloud.auth: "elastic:YOUR_PASSWORD"
These settings can be also specified at the command line, like this:
apm-server -e -E cloud.id="<cloud-id>" -E cloud.auth="<cloud.auth>"
cloud.id
editThe Cloud ID, which can be found in the Elasticsearch Service web console, is used by
APM Server to resolve the Elasticsearch and Kibana URLs. This setting
overwrites the output.elasticsearch.hosts
and setup.kibana.host
settings.
cloud.auth
editWhen specified, the cloud.auth
overwrites the output.elasticsearch.username
and
output.elasticsearch.password
settings. Because the Kibana settings inherit
the username and password from the Elasticsearch output, this can also be used
to set the setup.kibana.username
and setup.kibana.password
options.
On this page
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now