Elastic Agent to Logstash: Air-gapped environment
Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability This functionality is generally available and ready for production usage. 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.
Self-managed
Generally available
- Ingest model
-
All Elastic Stack components deployed inside a DMZ:
- Control path: Elastic Agent to Fleet to Elasticsearch
- Data path: Elastic Agent to Elasticsearch
- Control path: Elastic Agent to Fleet to Elasticsearch
- Use when
- Your self-managed Elastic Stack deployment has no access to outside networks
Info for air-gapped environments:
- Installing the Elastic Stack in an air-gapped environment
- Using a proxy server with Elastic Agent and Fleet
The Logstash geoip filter requires regular database updates to remain up-to-date with the latest information. If you are using the Logstash geoip filter plugin in an air-gapped environment, you can manage updates through a proxy, a custom endpoint, or manually. Check out Manage your own database updates for more info.