Elastic Agent to Logstash to Elasticsearch: Logstash as a proxy
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
- 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 Elastic Cloud. This approach helps reduce the number of firewall exceptions needed to forward data from large numbers of Elastic Agents.
Info on configuring Elastic Agent:
Info on Logstash and Logstash plugins:
Info on Elasticsearch: