- 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
- Set up Fleet Server
- Install Elastic Agents
- Install Fleet-managed Elastic Agents
- Install standalone Elastic Agents (advanced users)
- Install Elastic Agents in a containerized environment
- Installation layout
- Air-gapped environments
- Use 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
- Manage integrations
- Configure standalone Elastic Agents
- 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.
Run Elastic Agent on Amazon EKS managed by Fleet
editRun Elastic Agent on Amazon EKS managed by Fleet
editPlease follow the steps to run the Elastic Agent on Run Elastic Agent on Kubernetes managed by Fleet page.
Important notes:
editOn managed Kubernetes solutions like EKS, Elastic Agent has no access to several data sources. Find below the list of the non available data:
-
Metrics from Kubernetes control plane
components are not available. Consequently metrics are not available for
kube-scheduler
andkube-controller-manager
components. In this regard, the respective dashboards will not be populated with data. - Audit logs are available only on Kubernetes master nodes as well, hence cannot be collected by Elastic Agent.
-
Fields
orchestrator.cluster.name
andorchestrator.cluster.url
are not populated.orchestrator.cluster.name
field is used as a cluster selector for default Kubernetes dashboards, shipped with Kubernetes integration.In this regard, you can use
add_fields
processor to addorchestrator.cluster.name
andorchestrator.cluster.url
fields for each Kubernetes integration's component:Processors configuration.
- add_fields: target: orchestrator.cluster fields: name: clusterName url: clusterURL
On this page
Was this helpful?
Thank you for your feedback.