- Elastic Ingest Reference Architectures: other versions:
- Ingest architectures
- Elastic Agent to Elasticsearch
- Elastic Agent to Logstash to Elasticsearch
- Elastic Agent to Logstash (for enrichment) to Elasticsearch
- Elastic Agent to Logstash to Elasticsearch: Logstash Persistent Queue (PQ) for buffering
- Elastic Agent to Logstash to Elasticsearch: Logstash as a proxy
- Elastic Agent to Logstash for routing to multiple Elasticsearch clusters and additional destinations
- Elastic Agent to proxy to Elasticsearch
- Elastic Agent to Elasticsearch with Kafka as middleware message queue
- Logstash to Elasticsearch
- Elastic air-gapped architectures
Elastic Agent to Logstash to Elasticsearch: Logstash as a proxy
editElastic Agent to Logstash to Elasticsearch: Logstash as a proxy
edit
- Ingest model
-
Data path: Elastic Agent to Logstash as bridge to Elasticsearch on Elastic Stack network
Control path: Elastic Agent to Fleet Server to Elasticsearch - Use when
- Agents have network restrictions for connecting to Elasticsearch on Elastic Stack deployed outside of the agent network
- Example
- You can send data from multiple Elastic Agents through your demilitarized zone (DMZ) to Logstash, and then use Logstash as a proxy through your firewall to Elasticsearch Service. This approach helps reduce the number of firewall exceptions needed to forward data from large numbers of Elastic Agents.
Resources
editInfo on configuring Elastic Agent:
Info on Logstash and Logstash plugins:
Info on Elasticsearch:
On this page
Was this helpful?
Thank you for your feedback.