# Best practice for running Elastic Agents in EKS

**URL:** <https://discuss.elastic.co/t/best-practice-for-running-elastic-agents-in-eks/330931>\
**Category:** Elastic Agent\
**Created:** [April 27, 2023, 9:16am UTC](https://discuss.elastic.co/t/best-practice-for-running-elastic-agents-in-eks/330931 "2023-04-27T09:16:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikkoc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikkoc/32/118026_2.png) [@mikkoc](https://discuss.elastic.co/u/mikkoc)\
**Post date:** [April 27, 2023, 9:16am UTC](https://discuss.elastic.co/t/best-practice-for-running-elastic-agents-in-eks/330931/1 "2023-04-27T09:16:11Z")

</div>

Hello,  
We run Elastic Agents via Fleet in our EKS cluster, as DaemonSet, with about 20 nodes.

We want to monitor and collect AWS Cloudwatch metrics, in addition to Kubernetes logs on each node.

How do we go about installing the AWS integration without duplicating the Cloudwatch API calls 20 times? Do we need to setup a different Deployment with size = 1?

Or is there some way to instruct the Fleet agents to elect a leader that is in charge of AWS metrics collection?

Thanks  
Mikko

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 25, 2023, 9:16am UTC](https://discuss.elastic.co/t/best-practice-for-running-elastic-agents-in-eks/330931/2 "2023-05-25T09:16:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.