# Not able to use profiling on fargate enviroment

**URL:** <https://discuss.elastic.co/t/not-able-to-use-profiling-on-fargate-enviroment/350688>\
**Category:** Continuous Profiling\
**Created:** [January 9, 2024, 10:31pm UTC](https://discuss.elastic.co/t/not-able-to-use-profiling-on-fargate-enviroment/350688 "2024-01-09T22:31:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![julianep](https://avatars.discourse-cdn.com/v4/letter/j/df788c/32.png) [@julianep](https://discuss.elastic.co/u/julianep)\
**Post date:** [January 9, 2024, 10:31pm UTC](https://discuss.elastic.co/t/not-able-to-use-profiling-on-fargate-enviroment/350688/1 "2024-01-09T22:31:16Z")

</div>

I'm using the elastic agent to implement the Universal Profiling feature in our AWS ECS Fargate clusters, but I'm facing strange errors and we got stuck trying to get this working properly, i know this is related to ebpf, do someone have a workaround for this one?  
 ![unnamed](https://us1.discourse-cdn.com/elastic/original/3X/3/9/39c4a64361c02d7f916d69dfae4299e8e6de6455.png)

---

<div class="post-metadata">

**Author:** ![Florian\_Lehner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/florian_lehner/32/97221_2.png) [@Florian\_Lehner](https://discuss.elastic.co/u/Florian_Lehner)\
**Post date:** [January 15, 2024, 9:42am UTC](https://discuss.elastic.co/t/not-able-to-use-profiling-on-fargate-enviroment/350688/2 "2024-01-15T09:42:51Z")

</div>

Hi @julianep

At the moment it is not possible to use eBPF in the AWS Fargate environment. There is a request with [[Fargate] [request]: Provide the ability to use ebpf on fargate instances. · Issue #1027 · aws/containers-roadmap · GitHub](https://github.com/aws/containers-roadmap/issues/1027) to provide the ability to use eBPF on AWS Fargate instances.  
As Universal Profiling is building on eBPF, it is currently not possible to use Universal Profiling on AWS Fargate instances.

---

<div class="post-metadata">

**Author:** ![julianep](https://avatars.discourse-cdn.com/v4/letter/j/df788c/32.png) [@julianep](https://discuss.elastic.co/u/julianep)\
**Post date:** [January 25, 2024, 11:09pm UTC](https://discuss.elastic.co/t/not-able-to-use-profiling-on-fargate-enviroment/350688/3 "2024-01-25T23:09:41Z")

</div>

Hi @Florian_Lehner, thanks for the info, but there is some workaround we can do to start using profiling on fargate? even if we drop some metrics. some is better then nothing

---

<div class="post-metadata">

**Author:** ![Florian\_Lehner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/florian_lehner/32/97221_2.png) [@Florian\_Lehner](https://discuss.elastic.co/u/Florian_Lehner)\
**Post date:** [January 26, 2024, 6:40am UTC](https://discuss.elastic.co/t/not-able-to-use-profiling-on-fargate-enviroment/350688/4 "2024-01-26T06:40:00Z")

</div>

Unfortunately there is no workaround. On AWS Fargate environments eBPF is blocked and so Universal Profiling is not able to operate.

Please [[Fargate] [request]: Provide the ability to use ebpf on fargate instances. · Issue #1027 · aws/containers-roadmap · GitHub](https://github.com/aws/containers-roadmap/issues/1027) for updates, when eBPF will be available on AWS Fargate environments.

---

<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:** [February 6, 2024, 10:31pm UTC](https://discuss.elastic.co/t/not-able-to-use-profiling-on-fargate-enviroment/350688/5 "2024-02-06T22:31:58Z")

</div>

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