IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
Elastic Docs ›Elasticsearch Ingest Architectures [8.9]
« Elastic Agent to Logstash for routing to multiple Elasticsearch clusters and additional destinations Elastic Agent to Elasticsearch with Kafka as middleware message queue »

Elastic Agent to proxy to Elasticsearchedit

Image showing connections between Elastic Agent and Elasticsearch using a proxy when Fleet Server is managed by Elastic
Image showing connections between Elastic Agent and Elasticsearch using a proxy
Ingest model

Control path for Fleet Server on Elastic Cloud: Elastic Agent to proxy to Fleet Server to Elasticsearch
Control path for self-managed Fleet Server: Elastic Agent to Fleet Server to proxy to Elasticsearch
Data path: Elastic Agent to proxy to Elasticsearch
Use when
  • Network restrictions prevent connection between Elastic Agent network and network where Fleet Server and Elastic Stack are deployed, as when Fleet Server is deployed on Elastic Cloud
  • Network restrictions prevent connection between Elastic Agent and Fleet Server network and the network where Elastic Stack is deployed, as when Elastic Stack is deployed on Elastic Cloud

Resourcesedit

Info on Elastic Agent and agent integrations:

Info on using a proxy server:

Info on Elasticsearch:

« Elastic Agent to Logstash for routing to multiple Elasticsearch clusters and additional destinations Elastic Agent to Elasticsearch with Kafka as middleware message queue »