Open
Description
The Logstash documentation has various different areas that describe how to communicate to Elasticsearch and what credentials to use. However, this documentation is not full aligned and consistent across all of these areas. For example, some places talk about Cloud ID, API Keys and the usage of user/password.
As such, we need to align this documentation to provide a consistent experience. This means that in every place of the documentation we should ensure it aligns to our Security Configuration and examples reflect credentials that would be appropriate for each use case,.
Examples where a 'elastic' user is used:
- In filebeat / Kafka / Logstash docs: https://www.elastic.co/guide/en/logstash/current/use-ingest-pipelines.html#use-ingest-pipelines
- In filebeat modules docs: https://www.elastic.co/guide/en/logstash/current/use-ingest-pipelines.html#use-ingest-pipelines
- Modules documentation:
arcsight: https://www.elastic.co/guide/en/logstash/current/arcsight-module.html#configuring-arcsight
netflow: https://www.elastic.co/guide/en/logstash/current/netflow-module.html#netflow-module-config
azure: https://www.elastic.co/guide/en/logstash/current/azure-module.html#azure_config_options - Sample config file: https://github.com/elastic/logstash/blob/main/config/logstash-sample.conf#L14