# Beat autodiscover docker.sock permission denied on AWS ECS

**URL:** <https://discuss.elastic.co/t/beat-autodiscover-docker-sock-permission-denied-on-aws-ecs/114597>\
**Category:** Beats\
**Created:** [January 8, 2018, 6:42pm UTC](https://discuss.elastic.co/t/beat-autodiscover-docker-sock-permission-denied-on-aws-ecs/114597 "2018-01-08T18:42:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\
**Post date:** [January 9, 2018, 2:42pm UTC](https://discuss.elastic.co/t/beat-autodiscover-docker-sock-permission-denied-on-aws-ecs/114597/2 "2018-01-09T14:42:25Z")

</div>

Hi @iseyer_alx,

Our docker integration should work on ECS, we have reports from the community using it ([example](https://discuss.elastic.co/t/filebeat-and-metricbeat-produce-different-docker-metadata-for-same-container/107449)).

Could you share the full log output? Also, could you please detail how did you configure the container? The mount looks correct, did you keep it as writable, that's needed?, I'm also interested in how you configured the "run as root" part.

---

_[View the full topic](https://discuss.elastic.co/t/beat-autodiscover-docker-sock-permission-denied-on-aws-ecs/114597)._