Amazon Elastic Kubernetes Service (EKS) makes running Kubernetes on AWS simple and scalable. But as your workloads grow, so does the need for robust monitoring and observability. Enter Elastic Agent, a powerful, unified way to collect logs, metrics, and security data from your EKS clusters, all managed through Elastic Fleet. In this blog, we’ll walk through how to set up Elastic Agent on EKS, highlight key considerations, and share some tips for getting the most out of your monitoring stack.

https://static-www.elastic.co/v3/assets/bltefdd0b53724fa2ce/blt6bb8b4c3a1618135/68641ade02c701299db94eb2/Elastic-Agent-EKS-add-on.png,Elastic-Agent-EKS-add-on.png

Once the Elastic Agent is deployed in a pod, it automatically enrolls with Fleet, Elastic’s centralized management system, using the specified configuration values. After enrollment, Fleet provides full control over the agent, including its health status, configuration of integrations, and data ingestion. This setup enables centralized observability and security by ingesting and analyzing data in Elasticsearch, with visualization and management provided through Kibana.

https://static-www.elastic.co/v3/assets/bltefdd0b53724fa2ce/blt5e3108df764baac1/68641b1dbf423e9e9edd790b/fleet.png,fleet.pngStep-by-Step: Deploying Elastic Agent on Amazon EKS

Let’s break down the process, based on Elastic’s official documentation:

agent: fleet: enabled: true url: token:

Apply the configuration and deploy the add-on to your EKS cluster.

https://static-www.elastic.co/v3/assets/bltefdd0b53724fa2ce/blt7300dd074502dc14/68641b2bf44b170fd878aec2/elastic-agent.png,elastic-agent.png

Note: We recommend selecting configuration Override.