- Fleet and Elastic Agent Guide: other versions:
- Fleet and Elastic Agent overview
- Beats and Elastic Agent capabilities
- Quick starts
- Migrate from Beats to Elastic Agent
- Deployment models
- Install Elastic Agents
- Install Fleet-managed Elastic Agents
- Install standalone Elastic Agents (advanced users)
- Install Elastic Agents in a containerized environment
- Run Elastic Agent in a container
- Run Elastic Agent on Kubernetes managed by Fleet
- Run Elastic Agent on GKE managed by Fleet
- Run Elastic Agent on Amazon EKS managed by Fleet
- Run Elastic Agent on Azure AKS managed by Fleet
- Run Elastic Agent Standalone on Kubernetes
- Scaling Elastic Agent on Kubernetes
- Using a custom ingest pipeline with the Kubernetes Integration
- Environment variables
- Installation layout
- Air-gapped environments
- Using a proxy server with Elastic Agent and Fleet
- Uninstall Elastic Agents from edge hosts
- Start and stop Elastic Agents on edge hosts
- Elastic Agent configuration encryption
- Secure connections
- Manage Elastic Agents in Fleet
- Configure standalone Elastic Agents
- Create a standalone Elastic Agent policy
- Structure of a config file
- Inputs
- Providers
- Outputs
- SSL/TLS
- Logging
- Feature flags
- Agent download
- Config file examples
- Grant standalone Elastic Agents access to Elasticsearch
- Example: Use standalone Elastic Agent to monitor nginx
- Debug standalone Elastic Agents
- Kubernetes autodiscovery with Elastic Agent
- Monitoring
- Reference YAML
- Manage integrations
- Define processors
- Processor syntax
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_cef
- decode_csv_fields
- decode_duration
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- move_fields
- parse_aws_vpc_flow_log
- rate_limit
- registered_domain
- rename
- replace
- script
- syslog
- timestamp
- translate_sid
- truncate_fields
- urldecode
- Command reference
- Troubleshoot
- Release notes
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Deployment models
editDeployment models
editThere are various models for setting up Elastic Agents to work with Elasticsearch. The recommended approach is to use Fleet, a web-based UI in Kibana, to centrally manage all of your Elastic Agents and their policies. Using Fleet requires having an instance of Fleet Server that acts as the interface between the Fleet UI and your Elastic Agents.
For an overview of Fleet Server, including details about how it communicates with Elasticsearch, how to ensure high availability, and more, refer to What is Fleet Server?.
The requirements for setting up Fleet Server differ, depending on your particular deployment model:
- Elastic Cloud Serverless
- In a Serverless environment, Fleet Server is offered as a service, it is configured and scaled automatically without the need for any user intervention.
- Elasticsearch Service
- If you’re running Elasticsearch and Kibana hosted on Elasticsearch Service, no extra setup is required unless you want to scale your deployment. Elasticsearch Service runs a hosted version of Integrations Server that includes Fleet Server. For details about this deployment model, refer to Deploy on Elastic Cloud.
- Elasticsearch Service with Fleet Server on-premise
- When you use a hosted Elasticsearch Service deployment you may still choose to run Fleet Server on-premise. For details about this deployment model and set up instructions, refer to Deploy Fleet Server on-premises and Elasticsearch on Cloud.
- Self-managed
- For self-managed deployments, you must install and host Fleet Server yourself. For details about this deployment model and set up instructions, refer to Deploy on-premises and self-managed.
Was this helpful?
Thank you for your feedback.