Configuration example uses outdated security settings, specifically `cacert` and `force-peer` Topic: https://www.elastic.co/docs/reference/fleet/logstash-output Source: https://github.com/elastic/docs-content/blame/main/reference/fleet/logstash-output.md <img width="861" height="633" alt="Image" src="https://github.com/user-attachments/assets/665705c8-0421-4210-9e32-ecf5a06a4d3e" /> ### Resources and notes - https://www.elastic.co/docs/reference/logstash/plugins/plugins-inputs-elastic_agent - `ssl_verify_mode` replaced by [`ssl_client_authentication`](https://www.elastic.co/docs/reference/logstash/plugins/plugins-inputs-elastic_agent#plugins-inputs-elastic_agent-ssl_client_authentication) - https://www.elastic.co/docs/reference/logstash/plugins/plugins-outputs-elasticsearch - `cacert` replaced by [`ssl_certificate_authorities`](https://www.elastic.co/docs/reference/logstash/plugins/plugins-outputs-elasticsearch#plugins-outputs-elasticsearch-ssl_certificate_authorities) ### Related Scrub docsets for remaining instances of `cacert` (`docs-content`, `logstash`, `beats` repos)